Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Actively exploited sandbox RCE in all Chromium versions

nvd.nist.gov

Post reply on HN
Print view View original

321–330 of 528 posts

Re: Actively exploited sandbox RCE in all Chromium versions

#321

Post by phoghed »

robalni wrote: post #264
publlus_enigma wrote: post #55

Normalising running arbitrary code delivered over the internet (in the form of JavaScript and WASM), as a necessary condition for accessing most web pages may not have been one of the best decisions we have made.

That's basically the comment I was just going to write but you made me not need to. We need simpler protocols and formats, especially those that are used over the internet. I want everyone to really start fighting for this. I always use a browser that doesn't run any scripts (w3m) for both this reason and others. It hurts when I see websites that don't work without js. A bit funny though that this page is one of them…

We have them, and have had them for a long time. Nobody wants to use them.

Re: Actively exploited sandbox RCE in all Chromium versions

#322

Post by cannonpalms »

tclancy wrote: post #268
tantalor wrote: post #166

Earlier quoted context omitted.

The value of the report is dependent on the scarcity of the knowledge. If anybody can report it, the bid goes down.

How do you figure? The value of the report is, ethics aside, the same as the value of exploiting it. Doesn’t matter if I can conceive of it, it matters if I can exploit it.

Supply and demand has to be considered. The more parties aware of the vulnerability, the more attractive sellers (reporters) have to make their ask to the buyer (defender).

Re: Actively exploited sandbox RCE in all Chromium versions

#323

Post by notatoad »

neuroticnews25 wrote: post #320

I would guess it's now trivial for attackers to have an llm analyse every new commit to chromium repo linking to an issue that's 403 for security reasons, but maybe I'm missing something.

Equally trivial for Google to do the same thing. Is it trivial to do this in a way that exceeds googles own ability to detect flaws?

Re: Actively exploited sandbox RCE in all Chromium versions

#325

Post by doublerabbit »

dwattttt wrote: post #175
bawolff wrote: post #120

Earlier quoted context omitted.

Despite what people are saying here, chrome has a really excellent track record. Nobody is perfect. Switching just because chrome got exploited one time will likely result in you switching to something worse. If you're paranoid, disable JIT.

Or disable JS altogether, and enjoy many sites working much quicker. Many others fail & need to be selectively allowed, but it's been worth it.

If by quicker you mean blank content, I'll agree, it is worth it.

Re: Actively exploited sandbox RCE in all Chromium versions

#326

Post by throwaway27448 »

publlus_enigma wrote: post #55

Normalising running arbitrary code delivered over the internet (in the form of JavaScript and WASM), as a necessary condition for accessing most web pages may not have been one of the best decisions we have made.

At this point it doesn't even feel good to flex evidence of a warning

But, anyone who thinks we need JS for a functional internet is fucking retarded

Re: Actively exploited sandbox RCE in all Chromium versions

#327

Post by throwaway27448 »

phoghed wrote: post #321
robalni wrote: post #264

Earlier quoted context omitted.

That's basically the comment I was just going to write but you made me not need to. We need simpler protocols and formats, especially those that are used over the internet. I want everyone to really start fighting for this. I always use a browser that doesn't run any scripts (w3m) for both this reason and others. It hurts when I see websites that don't work without js. A bit funny though that this page is one of them…

We have them, and have had them for a long time. Nobody wants to use them.

> Nobody wants to use them.

Wikipedia is basically the most popular application of all time and it doesn't rely on javascript. People just generally don't give a shit about where their money goes.

Re: Actively exploited sandbox RCE in all Chromium versions

#328

Post by neuroticnews25 »

notatoad wrote: post #323
neuroticnews25 wrote: post #320

I would guess it's now trivial for attackers to have an llm analyse every new commit to chromium repo linking to an issue that's 403 for security reasons, but maybe I'm missing something.

Equally trivial for Google to do the same thing. Is it trivial to do this in a way that exceeds googles own ability to detect flaws?

What i meant is analyze fixes for already reported and fixed vulnerabilities before the updated version is pushed to users.

Re: Actively exploited sandbox RCE in all Chromium versions

#330

Post by Sharlin »

asveikau wrote: post #67
publlus_enigma wrote: post #55

Normalising running arbitrary code delivered over the internet (in the form of JavaScript and WASM), as a necessary condition for accessing most web pages may not have been one of the best decisions we have made.

I remember noticing this shift in nerd culture. In the early 2000s, it was common for people to say on places like Slashdot that they don't trust JavaScript and run their browser with it off. In the early 2010s, I noticed HN commenters thought this was insane, tinfoil hat type thinking.

In the early 2000s JS was used for silly novelty effects and some rudimentary DOM manipulation with `innerHTML`.

In the early 2010s you had to have JS enabled for many sites to work at all. The cost:benefit equation had became entirely different.

Post reply on HN