Live data from Hacker News

Escaping the Chrome Sandbox Through DevTools

ading.dev

61–70 of 85 posts

Re: Escaping the Chrome Sandbox Through DevTools

#61
post #3

Given the severity, I can't help but feel that this is underpaid at the scale Google is at. Chrome is so ubiquitous and vulnerabilities like these could hit hard. Last thing they need to do is to send the signal that it's better to sell these on the black market.

I've made lots of money with bug bounties over the years and mostly stopped this year in favor of private consulting. Companies will try anything to get out of paying, even through the major platforms. I once found a bug where I could access all of the names, addresses, emails, and phone numbers of all users for this new contest this company was running. I even found public announcements on Twitter. They told me this…

If they make excuses, sit on it, or dont pay out, release those bugs into the public domain, thats how this system works!

Re: Escaping the Chrome Sandbox Through DevTools

#62
> You may have noticed that the page URL gets substituted into ${url}, and so to prevent this from messing up the command, we can simply put it behind a # which makes it a comment

Is there some validation logic or something on this policy that the URL must be passed to the "alternative browser" somewhere in the AlternativeBrowserParameters?

Re: Escaping the Chrome Sandbox Through DevTools

#63
post #3

Given the severity, I can't help but feel that this is underpaid at the scale Google is at. Chrome is so ubiquitous and vulnerabilities like these could hit hard. Last thing they need to do is to send the signal that it's better to sell these on the black market.

Chrome needs to be rewritten in Rust asap

No it doesn't? This has nothing to do with memory safety. Its a logical error, which Rust physically cannot prevent.

Re: Escaping the Chrome Sandbox Through DevTools

#65

That's a neat vulnerability chain and a great writeup. Appreciated the breakdown of the vulnerable code as well! I'm always impressed by the simplicity of tricks like "Press F12 to try again", this is just so naughty :)

I live in Missouri; I pressed F12 once and the governor tried to get me arrested.

Re: Escaping the Chrome Sandbox Through DevTools

#66

Is it bad for Chrome to have vulnerabilities? I think long-term is really good. People need to get away from the browser monopoly (because it really is only Chrome here holding the power) and support the ecosystem

> Is it bad for Chrome to have vulnerabilities?

Yes, obviously it is. Is it bad for others/the public? Probably, but not as bad as it is for Chrome.

> because it really is only Chrome here holding the power

I'm not sure this is true. Apple pretty much forces usage of their browser engine on iOS, and heavily try to get people to use Safari on macOS. Windows push Edge pretty hard on their OS, and their browser engine is pretty much intertwined to the OS so you can't not use it. Both of them say they let you change the default, but various links in the OS would still open Edge/Safari even if you have the default browser changed. Not sure if that's on purpose or not.

Re: Escaping the Chrome Sandbox Through DevTools

#67
post #8

Earlier quoted context omitted.

I hate that every time a vulnerability is posted, someone has to argue about whether the bounty is high enough. It’s always followed by, "blah blah, they're pushing whitehats to sell it on the black market." Vulnerabilities will always sell for more on the black market because there’s an added cost for asking people to do immoral and likely illegal things. Comparing the two is meaningless. To give a straightforward a…

> The severity of a bug isn't based on how it could theoretically affect people but on how it actually does No, it's priced on demand and supply like anything else; bug bounties are priced to be the amount that Google thinks it takes to incentivise hunters to sell it to them, vs. to black hats.

There's a clear cut between selling it to Google and selling it to black hats. White hats mostly have a career in cyber security and they will not disclose a vulnerability to a compromised party regardless of the price. Cyber security researchers will like having their name attached to a CVE or a fix in a well known open source project which is arguably worth more than 20K to them. If someone finds out you sold a vulnerability, or exploit, to a hostile party, your career is over.

Re: Escaping the Chrome Sandbox Through DevTools

#68

>I'm Allen, a high school student with an interest in programming, web development, and cybersecurity. Very impressive!

Oh boy

What an amazing technical talent, sheer persistence, and excellent documentation and communication skills.

Not to mention the work ethic of responsible disclosure.

This person is going places!

Re: Escaping the Chrome Sandbox Through DevTools

#69
post #5

Earlier quoted context omitted.

If you can trick someone into installing a malicious extension with arbitrary permissions, you can already run arbitrary code on every webpage they visit, including their logged in bank, social media, etc. You think an attacker is right now thinking "Man, I know exactly how to make a lot of victims install an extension, but I can only steal their coinbase wallet and bank accounts, if only there was a way I could run…

Run calc.exe actually means steal money of everybody in their entire organization or blackmail the entire organization by encypting all the data they need to function.

If compromising a single machine of a user already compromises your entire orgs IT, you’re doing something wrong, right? Shouldn’t a normal user lack privileges to do this much damage to the network?

Re: Escaping the Chrome Sandbox Through DevTools

#70
post #59

Earlier quoted context omitted.

Chrome needs to be rewritten in Rust asap

Malwares are going to be written in rust; What difference does it make? Also Its not memory based vulnerability but policy based vulnerability.

But at least the vulnerability would be blazingly fast
Post reply on HN