Re:Comodo “Chromodo” Browser disables same origin policy
by twiss on Tuesday February 02, 2016 @06:32PM
(#11023584)
I don't understand the testcase they provide. It opens a window at https://ssl.comodo.com/ and sends a message to it with `postMessage`. However, the whole point of postMessage is to provide cross-origin communication. Continuing, the message they send is:
Apparently https://ssl.comodo.com/ used to then proceed to execute that code. However, this is not a vulnerability in the browser, but in that website. Am I missing something? Was Chromodo breaking the `messageEvent.origin` property, breaking same-origin checks in JavaScript? Seems far-fetched.
[ Parent
| on HN ]
Re:Comodo “Chromodo” Browser disables same origin policy
by lolc on Wednesday February 03, 2016 @05:27AM
(#11025739)
What postMessage() does is immaterial. This is where it should fail, referencing into another domain:
obj.postMessage
Re:Comodo “Chromodo” Browser disables same origin policy
by twiss on Wednesday February 03, 2016 @11:10AM
(#11027242)
No, that shouldn't fail. `postMessage` is not a random function defined inside the window at ssl.comodo.com. It's a function defined by the browser, available on every Window object, including ones returned by window.open():
https://developer.mozilla.org/docs/Web/API/Window/postMessag...