Probably business as usual, NSA just needed a little more time to finish a job.
Microsoft waited 6 months to patch actively exploited admin-to-kernel vulnerability
Submitted 8 months ago by ylai@lemmy.ml to technology@lemmy.world
https://www.theregister.com/2024/03/11/infosec_news_in_brief/
Comments
BeigeAgenda@lemmy.ca 8 months ago
autotldr@lemmings.world [bot] 8 months ago
This is the best summary I could come up with:
Infosec in brief Cybersecurity researchers informed Microsoft that Notorious North Korean hackers Lazarus Group discovered the “holy grail” of rootkit vulnerabilities in Windows last year, but Redmond still took six months to patch the problem.
Researchers at Avast said they informed Microsoft of a serious admin-to-kernel exploit in a driver associated with AppLocker, the app for whitelisting software built into Windows, in August of last year.
“This presented an ideal exploitation scenario, allowing the attacker to call an arbitrary kernel function with a high degree of control over the first argument.”
Avast claims Lazarus Group used the vulnerability to obtain read/write primitive on the Windows kernel and install their FudModule rootkit, but Microsoft’s opinion on the severity of admin-to-kernel exploits meant it didn’t prioritize the matter, waiting until February’s patch Tuesday to fix the issue, which it tagged as CVE-2024-21338, with a CVSS score of 8/10.
Of admin-to-kernel issues, Microsoft said administrative processes and users are part of Trusted Computing Base for Windows, and thus “not strong [sic] isolated from the kernel boundary.”
“By providing complementary security certifications, we aim to break down barriers and create opportunities for women in Jordan, fostering a more inclusive and diverse workforce,” OpenSSF said.
The original article contains 705 words, the summary contains 200 words. Saved 72%. I’m a bot and I’m open source!
RavuAlHemio@lemmy.world 8 months ago
Doesn’t having admin privileges mean you can load any driver into the kernel anyway, including blatantly malicious drivers?
Limonene@lemmy.world 8 months ago
Microsoft has enforced mandatory digital signatures for drivers, and getting a digital signing key from Microsoft costs a ton of money. So, presumably they do care.
In contrast, consider nProtect GameGuard, the anti-cheat system in Helldivers 2. It is a rootkit, and runs in the kernel. Why does Microsoft permit this? Shouldn’t this be blocked? It must be using either an exploit like the article, or a properly signed driver. Either way, Microsoft could fix it – by patching the exploit, or revoking the signing key.
The fact that Microsoft hasn’t done anything about malicious anticheat rootkits is a sign that they really don’t care. They just want their payment.
SteveTech@programming.dev 8 months ago
I might be completely wrong, but I’ve heard that a key is only a few hundred dollars, and once you’ve got it you can sign whatever you want. I think ReactOS also used to offer free driver signing for open source projects.
So I guess if ReactOS can afford one, so can most anti-cheat companies.
henfredemars@infosec.pub 8 months ago
I’m not sure that’s necessarily true with enforcement of driver signing.
hddsx@lemmy.ca 8 months ago
Why’s that? I thought admin could override that
Car@lemmy.dbzer0.com 8 months ago
Pretty much. This is one particular form of damage control for an attacker who has the keys to your system. I think there were more urgent security concerns that occur in the untrusted zone.