A library Windows host runs an outdated third-party kernel driver. Why should privilege-escalation enumeration include that class of software?
Select an answer to reveal the explanation.
Short Explanation
Third-party drivers sit down in the basement with the kernel—when they are old and buggy, the whole house shakes. Enumerators include them because elevated driver flaws are a real priv-esc class. Age is not just about nicer Wi-Fi bars.
Full Explanation
Kernel-mode and other highly privileged third-party drivers expand the trusted computing base beyond inbox Microsoft components. Outdated vendor drivers have historically hosted local privilege-escalation vulnerabilities, so inventory and version awareness belong in Windows priv-esc enumeration. They are not automatically low-integrity, not universally out of scope, and not merely cosmetic for wireless signal. Note versions, correlating known issue classes carefully within RoE.