2,548 karma · joined January 7, 2020
Shell32.dll has the code for it under QueryUserAssocAndVerifyHash I believe. Perhaps they've interfered with the hash interpretation for Chrome or Chrome is hooking into it in a different way - Firefox directly computes and writes a new hash to the registry.
For people who are not spies or hoarding millions worth of cryptocurrencies on their desktop PCs, they're not likely running across zero day exploits on the regular. They are however running across trackers galore and Firefox's tracking protection and anti-fingerprinting features are likely to make a larger difference in practice for all but the most targeted of individuals.
I feel like this is probably a pretty bad example, generally the "art" in video games comes from things like dialogue, storytelling, level design, graphical art, not the physics engine or the renderer. There is simply not art there, it's more engineering.
There's little more art in the code portion of video games than there is in a jet engine.
Why, more wealth and automation and productivity growth to no end of course.
The higher risk thing tends to be downloading cracks from torrents or usenet where there's 3rd parties between you and a scene group.
If you can use Windows without it getting full of malware, you can handle unpatched Android LPEs too.
Keep in mind, Webview, browsers, email clients, etc are patched via app update mechanisms.
The rate of finding exploits and what the definition of a vulnerability is really what has changed - now the definition of is much broader while at the same time, exploitability has dropped off due to mitigation in modern operating systems, compilers and CPUs. Overall, we get far more exploits, but far less of significance.
Yes, this is still a risk - if you tend to install random apks from the internet and disable Play Protect or run across an undetected modification of the relevant exploit code. But most users don't do that.
An average user installing apps from Play Store has nothing to worry about for those. That's kind of the point.
It's great for these devices to be patched - I'd love it if Google would take more control over the ecosystem to be able to patch this sort of thing, but it's much worse for users to just throw out otherwise working devices with limited-to-no real-world security issues.
For sure, if you're paranoid or a high-value target, update, buy a new phone. But normal users don't need to care unless there's actually something on the line.
Your threat model might be different but I don't get out of bed for anything but RCE personally, let alone spend a penny.
Basically, don't put that on your CV unless you know the company doesn't filter resumes through HR and has somewhat technical management.
L3 is weak enough that you can dump it by just hooking the decoders.
App stores are too polluted with garbage now, they went from being a unique selling point of mobile platforms to entirely useless and I think IAPs are largely to blame.
While it's true that malware could hide well theoretically, I'll also add that in my experience investigating malware infections from friends and family and occasionally hunting for malware myself, samples attached to cracked software tend to be things like miners, iStealer, script kiddie RATs, etc using simple "binders" - which are usually incredibly obvious, like extract the real executable into %temp% or the usual RunPE gimmick. People posting malware on torrent sites are not exactly APTs using spear phishing attacks.
What's the driving factor for that limitation?