r/javascript • u/operationRareSteak • Mar 27 '22
Chrome vulnerability reported for 3.2 billion users
https://www.forbes.com/sites/daveywinder/2022/03/26/google-confirms-emergency-security-update-for-32-billion-chrome-users-attacks-underway/?sh=c336c5daaa2e10
u/Panda_Mon Mar 28 '22
Will a smart person please provide a step by step on how to defend against this for the heathen peasants. We know only the hoe and plow
1
4
u/sc3w Mar 28 '22
If this is at chromium level than that means many other apps built with ElectronJS are affected, like Spotify, Notion, VSCode to name a few.
5
u/Nasuadax Mar 28 '22
A big difference is that it is a lot harder to get malicious code into those apps than it is to get the malicious code in a browser that accesses any possible website. Not saying it is impossible, but since they are restricted in what domains they access, it becomes harder (ignoring stuff like twitch that has user input ofc, but how would you get malicous code on someone elses pc in spotify for example)
2
u/sc3w Mar 28 '22
Obviously, it's much harder to do it but probably not impossible either and considering that ElectronJS is used for many apps, I think it's not something to ignore.
4
u/Darkmaster85845 Mar 27 '22
Am I OK if I use brave?
98
u/freecodeio Mar 27 '22
It looks like it's a V8 vulnerability so brave, edge, everything chromium is affected.
7
u/MachaHack Mar 27 '22
Also the platform web view if you're using Chromebooks, Windows 11, or Android. Maybe Windows 10, not sure if the Win10 webview has been ported transparently from mshtml to edge.
1
u/klawiatura_stefan Mar 28 '22
Unless your default browser is set to something else, Firefox for example. At least it works that way on Android.
2
25
u/bregottextrasaltat Mar 27 '22
What a great idea for most browsers to share the engine huh
60
Mar 27 '22
I mean, when it is a shared engine they all get the benefit of a fix to a major security hole, as opposed to tracking and managine every security hole in their own platform alone. I agree that competition is good, but every product has a security hole at some point. Especially browser engines.
13
u/skylarmt Mar 27 '22
Monocultures are generally bad, whether it's browsers, bananas, or inbreeding.
When a single company controls it all, it's even worse, because they get to set the rules and what they want is often not what is best for everyone.
14
u/the_aligator6 Mar 28 '22 edited Mar 28 '22
according to who? you? monoculture is bad as an agricultural practice due to soil degredation. you can't just blindly apply that to software, that makes literally no sense.
"when a single company controls it"
this literally has nothing to do with Google or Chrome. Do you know anything about V8? how the governance of the project is structured and how many companies are involved? do you have any idea how fucking hard it is to build browsers that comply with 100% of the specs and provide useable performance from scratch? go try building a browser. look at servo. go spend a few weeks reading the docs and specs. this shit isn't the fault of monopolistic governance, and having multiple competing implementations of a spec/protocol doesn't just magically make your problems go away. cooperation is what we need, not competition. solid legal and open source governance policies with transparency and common sense applied to funding and decision making wins out most of the time over competing implementations.
6
u/MachineOfScreams Mar 28 '22
Well to be fair, Google can drive a lot of the features and desires due to having the biggest browser on the market. It means all their built in assumptions and desires drive the market and, if you are a smaller fork of that browser, you are going to look to ape as much of the Google chrome experience as possible including apps. Google doesn’t have to outright own the underlying code to make it the dominant speaker in standards, the direction of web design, etc. Just need to be the biggest fish in the pond.
1
u/the_aligator6 Mar 28 '22
can you provide evidence that this is actually happening? so far all I see is speculation that it might be happening.
from my perspective, the control they exercise comes from their market share of the browser market and overall web traffic. the way they exercise that control seems to largely happen outside of the development of chromium itself. look at the AMP, or FLOC, Privacy Sandbox or Quic. Google exerts most of its power well within the confines of the web, or within W3C and IETF and other industry groups, or in Washington. I don't think picking on chromium is fair. Chromium is a relatively benign project, very little controversial power moves from google come from that angle. not stop say there aren't any, but FAR more is done on their home turf, within chrome. when you control 67% or whatever it is now of the market share, and god knows how much of the total number of endpoints and volume of web traffic, your battles happen at a higher level than the implementation of the guts of web rendering or JavaScript execution. it happens at W3C level and far beyond.
7
Mar 28 '22
outside of the development of chromium itself look at [...] FLOC
Here is the code for FLOC in chromium: https://source.chromium.org/chromium/chromium/src/+/master:components/federated_learning/?q=federated%20learning&ss=chromium%2Fchromium%2Fsrc
If you look around, you will also find other detrimental features that Google pushes other browsers to adopt, like Manifest v3, Idle Detection, Keyboard Map API, etc...
1
u/the_aligator6 Mar 28 '22
the implementation follows the spec, right?
https://wicg.github.io/floc https://www.w3.org/2021/02/23-web-adv-minutes.html#t02
it seems like the battleground is W3C, not Chromium.
the only way to know for sure it to dig deeper into the timeline.
→ More replies (0)1
u/MachineOfScreams Mar 28 '22
I am not saying Google Chrome is seeking to be a malevolent force on the market. That would be assigning ethical values to it that I am not comfortable with. What I am saying is that by being the biggest fish in the pond you can, as was pointed out, push your own perspective either purposefully or inadvertently.
And if Google is pushing hard on certain features and adoptions of them, and it happens to be the biggest browser game on the market, then it has a lot more say than other browsers (for what it’s worth, Firefox tends to be better at allowing you to block any and all scripts and ads if you want to. Google and most of its forks don’t for obvious reasons of ad revenue.)
-4
u/Captain-Crayg Mar 28 '22 edited Mar 28 '22
Chromium is open sourced. No-one controls it.
1
u/skylarmt Mar 28 '22
Google controls it. They deign to accept contributions from others too.
Besides, almost nobody uses Chromium, they use Chrome, which is the result of Google adding all their spyware and DRM.
-2
u/bregottextrasaltat Mar 27 '22
Agreed, but I think also with one engine it's a bigger target and more trusted
-2
Mar 27 '22
Yeah but it's so much easier on devs to write code for. There are tradeoffs of course, but I'm all in favor of fewer engines
11
u/Brachamul Mar 27 '22
Disagree. Easiness of coding is related to how browsers follow standards. We could perfectly have multiple engines following the same standards.
Currently Google does whatever it wants and Apple actively stifles Safari on Mac and all browsers on iPhones because it's afraid of what the web could do to its appstore profit margins.
5
u/radapex Mar 27 '22
Easiness of coding is related to how browsers follow standards. We could perfectly have multiple engines following the same standards.
Part of the problem there is that the standards aren't always well-defined.
contextmenuevents, for example. Firefox and Chrome's implementations are technically both W3C-compliant but they behave differently. The specification says that it must be dispatched aftermousedown, and optionally before or aftermouseup. In Firefox, it also dispatches aclickevent; but in Chrome, there is noclick.4
u/Brachamul Mar 27 '22
Standards can be defined better, though. Just because the standards are improvable, does not mean the solution is a single browser engine.
1
u/radapex Mar 27 '22
Absolutely. I assuming it's more about companies not wanting to have to sink time and money into trying to compete with V8 - so instead they just use it. It's not like there's a lot of financial incentive for them to create their own engines.
1
u/Nasuadax Mar 28 '22
Relying on implementation details rather then specification details has always been ill advised, even outside of web development. Relying on such behaviors is asking to get troubles over time. The fact that you have monoculture, softens the punishment, as you will only notice it when the browser changes something it hasnt changed for a while. But they still could do it...
1
u/radapex Mar 28 '22
The problem isn't necessarily relying on implementation details over specification, it's that some browsers haven't been keeping up with specifications and that would likely be a bigger problem with more engines.
Firefox has fixed the aforementioned
contextmenu+clickissue within the last year or two (I can't recall exactly when). The standard forclickstates that it only be fired on primary button click, so the Chromium implementation was correct but if you wanted to do something like a custom context menu that closes on click you'd have to work around the Firefox implementation. (binding theclickhandler right away would immediately close the context menu, because theclickevent would be dispatched immediately aftercontextmenu*)*Firefox has also, just in their latest release version (98), started supporting
<dialog>without requiring users change browser flags to enable it.<dialog>has been in the standards since at least 2014, and has been supported in Chromium-based browsers for years.2
u/HeinousTugboat Mar 27 '22
I'm all in favor of fewer engines
There's only 3 major ones. How many fewer do you want?
1
1
Mar 27 '22
Yep so instead of one Megacorp having it's eyes on a project, it has 2 Megacorps, lots of open source contributors, and a few small companies' eyes on it!
I get that monocultures can be bad but it's open source and anyone can fork it if they want so it's not like any drawback of a monopoly will really exist. It just lowers the bar for competition to do everything you do just as well with some change that addresses a drawback (like Brave with anti-tracking stuff)
-2
-2
0
1
-16
-5
Mar 27 '22
Nuts to WASM. I'm don't want to run arbitrary compiled code in my browser.
8
u/eternaloctober Mar 27 '22
You would rather download it and run it without your browser where there are no restrictions?
1
u/voidvector Mar 28 '22
A previous CVE of same type (linked by someone in the thread) has a POC code that is pure JS.
69
u/freecodeio Mar 27 '22
Can anyone share more technical details? Looks like it's related to "type check confusion" in WASM, but it doesn't say if it's RCE or what type of attack.