4 ms·
and shortly thereafter, a malicious service was installed on the researcher’s system and an in-memory backdoor would begin beaconing to an actor-owned command a
by userbinator 6y ago
and shortly thereafter, a malicious service was installed on the researcher’s system and an in-memory backdoor would begin beaconing to an actor-owned command and control server. At the time of these visits, the victim systems were running fully patched and up-to-date Windows 10 and Chrome browser versions.
I am almost willing to bet $$$ that they would be fine if they had JS disabled.
That also reminds me of something I remember reading about many years ago on an RE site: "You hear about all the bugs they fix in each update. You don't hear about all the new ones they introduced."
- gruez 6y ago>I am almost willing to bet $$$ that they would be fine if they had JS disabled. The problem is that you eventually have to enable scripts when you encounter a site that refuses to work with scripts disabled. There are enough of such sites around that most people would instinctively enable scripts whenever they see a broken site, which nullifies any security benefit.
- userbinator 6y agoIf anything, security researchers should not be "most people". They should know better than to let sites execute untrusted code. Of course, I believe Google is complicit in this somewhat, since its own intrusive tracking needs JS, and so it encourages everyone to make sites that require it and users to leave it on by default.
- mappu 6y ago>I am almost willing to bet $$$ that they would be fine if they had JS disabled. The attack vector was spearphishing followed by convincing the target to compile a project, where the makefile contained malware. No JS involved.
- dotty- 6y agoFrom the blog post: >In addition to targeting users via social engineering, we have also observed several cases where researchers have been compromised after visiting the actors’ blog. Aka, they were compromised after simply visiting a malicious blog. This is why the blog post emphasizes the Chrome Vulnerability Program, and specifically mentions that the victim was running a fully patched Windows 10 machine and fully patched Chrome. >At the time of these visits, the victim systems were running fully patched and up-to-date Windows 10 and Chrome browser versions. RCE exploits on web browsers are typically written in JS. I would also bet $$$ that if they had JS disabled, they would not have been compromised.
- deathanatos 6y agoThe article notes that there appear to have been exploits from browsing to the attackers' blogs in addition to the malware-laden software project.
- smnrchrds 6y ago> I am almost willing to bet $$$ that they would be fine if they had JS disabled. I am fully willing to bet $$$$ that they would be fine if they had air gapped their computer. Unfortunately, disabling JS is only marginally more practical than completely foregoing access to the web; and it is only going to get worse as more sites and services rely on JS.
- superkuh 6y agoIt really depends on what you do. Amazon.com, for example, works perfectly fine with javascript disabled. They do it because they care about selling to everyone and know that even people with old computers and old software buy things. Web devs keep repeating to themselves that no one browses with JS off but you can't see the ones that have it off if all you use to survey is JS itself.
- g_p 6y agoGov.UK is built around an assumption users have no or broken JavaScript, based on some of their research into how people use the site. When running at scale, they found about 1 in 93 visitors didn't have working JavaScript. [1] Mid startup hustle it makes sense for people to start ignoring this. But if you adopt a mindset of serving users, you'll quickly see why they went with this approach - progressive enhancement of the site based on the capabilities that work, with a fully functional experience extending from lynx and upwards. [2] [1] https://gds.blog.gov.uk/2013/10/21/how-many-people-are-missing-out-on-javascript-enhancement/ https://gds.blog.gov.uk/2013/10/21/how-many-people-are-missi... [2] https://technology.blog.gov.uk/2016/09/19/why-we-use-progressive-enhancement-to-build-gov-uk/ https://technology.blog.gov.uk/2016/09/19/why-we-use-progres...
- tclancy 6y ago(Disclosure: I am not in any way a security researcher) > I am almost willing to bet $$$ that they would be fine if they had JS disabled I would guess that's because you do and that's what you use as a proxy to feel safe about the unsafe web. All of us even slightly aware of the security problems of browsing the web have something (for myself I immediately thought, I should add those domain names to my PiHole, just to be safe), but that's the problem with asymmetry: it costs you a lot to defend against everything; it costs a determined attacker very little in a marginal cost sense to spread their efforts across threat vectors. You're pretty sure disabling JS makes things safe. Do you allow CSS? That's another vector. What about all those cool new HTML5 apis we have now? Heck, it's tough to get developers to think at all about accessibility, what are the odds the developers who have to support that under-appreciated field put in a ton of extra time to make sure the features are fuzz tested? Anyone tested what you can do with the subtitle track to an HTML5 video player? I bought a copy of The Tangled Web a decade ago and never finished it because the whole thing was just too depressing to really come to grips with and instead I too have uBlock, a PiHole, some other Chrome extensions and a Mac as a sort of double-condom to make me feel safe without making me much safer. We are all the US military, happily stockpiling the wrong assets to fight the last war.
- everybodyknows 6y ago>I too have uBlock, ... Did you mean “uBlock Origin”, from the original author of uBlock? https://news.ycombinator.com/item?id=24534778 https://news.ycombinator.com/item?id=24534778
- tclancy 6y agoYes. Good point about the clarification!
- albntomat0 6y agoTake a look at the most recent stable release notes for Chrome. I don't have a full list of which ones are in the renderer processes vs which ones are in the browser process. That said, it seems like a good number would affect Chrome without Javascript https://chromereleases.googleblog.com/2021/01/stable-channel-update-for-desktop_19.html https://chromereleases.googleblog.com/2021/01/stable-channel...