• besselj@lemmy.ca
    link
    fedilink
    English
    arrow-up
    40
    ·
    8 months ago

    Sounds like the OS is put together with duct tape if deleting an empty folder can break things so easily

      • besselj@lemmy.ca
        link
        fedilink
        English
        arrow-up
        14
        ·
        8 months ago

        Another possible explanation from Hanlon’s razor: MS is going all-in on vibe coding

      • adarza@lemmy.ca
        link
        fedilink
        English
        arrow-up
        5
        ·
        8 months ago

        it’s nothing ‘new’. i have encountered empty inetpub folders frequently, on systems with no business having it in the first place… for years now.

        • CameronDev@programming.dev
          link
          fedilink
          English
          arrow-up
          4
          ·
          edit-2
          8 months ago

          I wonder if they were infected with something that was exploiting that CVE?

          Edit: Here is another tinfoil theory: the windows security subsystems special cases inetpub to allow all executables. If the path doesn’t exist, attackers can drop binaries in there to bypass security/codesigning etc. By creating it as SYSTEM, MS is ensuring that it can’t be written to without SYSTEM privs?

          • sylver_dragon@lemmy.world
            link
            fedilink
            English
            arrow-up
            3
            ·
            8 months ago

            Edit: Here is another tinfoil theory: the windows security subsystems special cases inetpub to allow all executables. If the path doesn’t exist, attackers can drop binaries in there to bypass security/codesigning etc. By creating it as SYSTEM, MS is ensuring that it can’t be written to without SYSTEM privs?

            Ya, I’d bet on something similar. According to the CVE, the vulnerability is around “Improper link resolution before file access”. My bet is that there is something hardcoded somewhere which assumes the existence of this folder. If it doesn’t exist, this can let the attacker get something in place which then gets executed with SYSTEM permissions, leading to privilege escalation. Not the worst thing in the world, for most users. But, it would be a problem in an enterprise environment where part of the security model is users not having local admin.

  • drspod@lemmy.ml
    link
    fedilink
    English
    arrow-up
    17
    ·
    8 months ago

    You’re telling me that enterprise CTOs trust this company to run their entire IT infrastructure?