Skip navigation
Forget vulnerable drivers - Admin is all you need
0:00 / 2:47

Forget vulnerable drivers - Admin is all you need

Gabriel Landau

@GabrielLandau4K followers

Visit on X
369 likesDownloadOriginal post

96,605 views

Forget vulnerable drivers - Admin is all you need Article ๐Ÿ‘‰ ๐Ÿ‘‡ Demo - enable sound ๐Ÿ”Š

21 Comments

Comments from the original post on X (Twitter)

  • Mike Felch (Stay Ready)'s profile picture

    @ustayready

    @richinseattle You can tell people have limited knowledge of EDR internals and havenโ€™t been on a red team engagement just by their comments. This is solid work, well done.

    23 likes

  • namazso's profile picture

    @namazso

    Have to side with MS here, admin to kernel is not a security boundary. If you have admin, you can just uninstall the latest cumulative update and exploit one of the dozens of exploits that get patched in them anyway. Maybe don't give out admin like candy?

    20 likes

  • Gabriel Landau's profile picture

    @GabrielLandau

    Yes admin to kernel is not a serviceable boundary per MSRC guidelines. I said that in both the video and the article. Thatโ€™s one of the things Iโ€™m questioning. As for downgrade attacks, perhaps the ability to downgrade could be forfeit via config, just like how you can forfeit the ability to change the boot loader and parts of the BCD by enabling Secure Boot - just a thought. Microsoft has smart people with experience mitigating downgrade attacks on the Xbox platform. Iโ€™m sure theyโ€™d come up with something if put in a room together.

    5 likes

  • namazso's profile picture

    @namazso

    And I'm replying to that questioning. Fixing your system if (when) it gets hosed by a broken update is kind of the point of admin though. You should be instead asking why you need admin or give people admin in the first place.

    1 like

  • Gabriel Landau's profile picture

    @GabrielLandau

    > if (when) it gets hosed I haven't needed to uninstall any updates from my last two machines, since about 2018. If that were to occur under my aforementioned scheme, I would go ahead and turn off Secure Boot, downgrade, then turn it back on. Alternatively, downgrades could be done keeping SecureBoot enabled through some sort of VTL1 recovery mode that boots off an RO partition protected by the hypervisor. I haven't wargamed the Secure Boot thing. It was just spitballing. Folks like you who don't care about downgrades could choose not to turn it on, just like you could choose to not enable Secure Boot, VBS, or Tamper Protection.

    1 like

  • namazso's profile picture

    @namazso

    So you're saying undoing updates is something a higher privileged "Admin 2" group should have access to, but the ability to install device drivers is something the janitor must have? I don't see what would guarantee you not just handing out those higher privileges to anyone too.

  • Gabriel Landau's profile picture

    @GabrielLandau

    Have you heard of the RunAsPPL UEFI lock that Microsoft has been shipping since 2013? Once enabled, an Admin cannot turn it off. Disabling it requires physical access. This would be similar to that:

    2 likes

  • Yarden Shafir's profile picture

    @yarden_shafir

    While itโ€™s true that admin->kernel is not a boundary Microsoft is working on enforcing security through adminless mode. Hopefully thatโ€™ll get shipped and admin will not be the default state of everything anymore.

    10 likes

  • Gabriel Landau's profile picture

    @GabrielLandau

    Yep I agree, and reference Adminless in the article :) How many years will it be until Adminless is the default everywhere. How many environments will it be incompatible/bothersome in? How many bad guys will be able to get Admin anyway via AAD/Kerberos/Potato tricks anyway? I guess we'll see in due time.

    2 likes

  • Yarden Shafir's profile picture

    @yarden_shafir

    I donโ€™t always agree with Microsoftโ€™s choices around which bugs they acknowledge/fix. But I also think chasing every admin->kernel bug is a hopeless cause and sometimes it really is better to use those resources for something else.

    5 likes

  • Gabriel Landau's profile picture

    @GabrielLandau

    > chasing every admin->kernel bug How many instant-EDR-kill admin->kernel R/W bugs are we talking about here? Not BYOVD, which are already being addressed elsewhere.

    1 like

  • Yarden Shafir's profile picture

    @yarden_shafir

    I do remember a few from the last few years and the fixes werenโ€™t always trivial. Not saying the decision is always correct, but this is still just one category of bugs out of many. I understand why itโ€™s not always top priority unless seen ITW.

    1 like

  • Alex's profile picture

    @appcustodian

    hackers hate this one neat trick: just already have admin lol

    7 likes

  • Gabriel Landau's profile picture

    @GabrielLandau

    Right, the article is about Admin->Kernel

    5 likes

  • Alex's profile picture

    @appcustodian

    which microsoft said is not a security boundary... it's cool that you want to argue otherwise but good luck fixing admin<->kernel and its infinite web of attack surface

    1 like

  • The Haagโ„ข's profile picture

    @M_haggis

    @dez_ This is awesome @GabrielLandau ! Thank you for sharing!

    3 likes

  • Artem I. Baranov's profile picture

    @artem_i_baranov

    Your new masterpiece in Windows Internals?) ๐Ÿ‘

    2 likes

  • KrisB's profile picture

    @krisbowe

    Nice work. Thanks for sharing

    1 like

  • NEE's profile picture

    @4pfsec

    Appreciate the share, great repo for learning!

  • Eddie Kavanagh's profile picture

    @eddiekavanagh

    Cheers mate, the more I learn the further away I get from sanity and logic. It's madness held up on hope, thoughts and prayers.