[srcmap]

Is this issue equivalent of setuid 4701 on executable owned by root in Linux?

What's the easiest way to scan whole windows file system for directories with this issue?

[hjek]

> What's the easiest way to scan whole windows file system for directories with this issue?

    tree c:\ /f  prn

Source: https://docs.microsoft.com/en-us/windows-server/administrati...

[cjbprime]

(It wouldn't help to scan the filesystem, since the way the vulnerability works is that the driver will be automatically downloaded and run when a peripheral's plugged in.)