Discussion
Search code, repositories, users, issues, pull requests...
ranger_danger: > normally I would just drop the PoC code and let people figure it outLooks like that's exactly what they did though?Or maybe they just meant that they don't usually explain how it works?
kijin: Tney gave it a sexy name and set up a website about it (a github repo, at any rate), instead of just talking about it in a mailing list and getting a CVE like a proper bearded security researcher.
labelbabyjunior: A local privilege escalation to root via an exploitable service?Doesn't Linux have one of these CVEs...each week?
egeozcan: I wonder why Windows Defender has the privilege to alter the system files. Read them for analysis? Sure! Reset (as in, call some windows API to have it replaced with the original), why not? But being able to write sounds like a bad idea.However, I don't know what I'm talking about so take it with a grain of salt!
EvanAnderson: AV had traditionally run as SYSTEM on Windows (and, in the past, often had kernel mode drivers too). I've always thought it was a terrible idea. It opens up exciting new attack surfaces. Kaspersky and McAfee both had privilege escalation vulnerabilities that I can recall. There have been a ton in multiple products over the years.
labelbabyjunior: They kind of have to, though.If malware exploits a privilege escalation vuln, what's the AV going to do about it when it's reduced to the software equivalent of a UK police officer? Observe and report? Stop or I'll say "stop" again?AV requires great power, which requires great responsibility. The second part is what often eludes AV developers.
labelbabyjunior: Some files under Windows are protected as the TrustedInstaller user, which is a more restrictive level of permissions than SYSTEM.
