Closed GoogleCodeExporter closed 8 years ago
I've attached a working exploit for this issue. I haven't received an
acknowledgement or response from Comodo, so I sent this reply:
FYI, I still haven't got a response. The same origin policy is basically
disabled for all of your customers, which means there is no security on the
web....this is about as bad as it gets. If the impact isn't clear to you,
please let me know.
This vulnerability is bad enough to start paging people.
Original comment by tav...@google.com
on 25 Jan 2016 at 7:19
Attachments:
Comodo replied that they're planning a hotfix for this issue within a day, but
the other open issues may take weeks to fix.
I replied that I noticed their scan process is not using ASLR, which probably
isn't a good sign going forward, and I'm planning to start a more thorough
audit next week.
Original comment by tav...@google.com
on 29 Jan 2016 at 5:15
[deleted comment]
[deleted comment]
It looks like Comodo pushed a change that removes the "execCode" API that I was
using in my exploit.
This is obviously an incorrect fix, and a trivial change makes the
vulnerability still exploitable. After "discussion" with Comodo (I can't really
get any response from them, but I'm trying), I'll consider this bug fixed and
file a new bug with the trivial bypass of their fix as a new issue.
The deleted comments above contained discussion about the bypass, I'll move
them into a new issue.
Original comment by tav...@google.com
on 2 Feb 2016 at 6:46
Discussion about the incorrect fix is in issue 713.
Original comment by tav...@google.com
on 2 Feb 2016 at 6:52
Original comment by tav...@google.com
on 2 Feb 2016 at 6:53
"After "discussion" with Comodo (I can't really get any response from them, but
I'm trying)"
Hopefully this being posted on HackerNews will help. If not, rampant
exploitation of Comodo browsers ought to incentivize companies to cancel their
subscriptions and Comodo will lose money.
Original comment by kobrasre...@gmail.com
on 2 Feb 2016 at 7:35
toppest of keks, my friend.
There's plenty of evidence of the shadiness of Chromodo, it gets pushed via the
kind of PUP bundler networks that also push winlocker trojans of Indian origin.
Original comment by l33t...@gmail.com
on 2 Feb 2016 at 8:36
Original comment by tav...@google.com
on 2 Feb 2016 at 8:38
Original issue reported on code.google.com by
tav...@google.com
on 22 Jan 2016 at 12:49Attachments: