• JelleWho@lemmy.world
    link
    fedilink
    English
    arrow-up
    56
    arrow-down
    2
    ·
    1 day ago

    For a second I though this was something bad for my computer. But is mainly a server permissions issue it seems. Will patch my server when I’m home though

    • bookmeat@fedinsfw.app
      link
      fedilink
      English
      arrow-up
      26
      arrow-down
      2
      ·
      23 hours ago

      It affects any device that can use raw sockets in the kernel. Patch everything.

    • drkt@scribe.disroot.org
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      2
      ·
      23 hours ago

      What do you mean? If you use Linux on your computer, it’s also relevant. Any program can quietly drop a root shell from any privilege level in 10 lines of python.

      • ipp0@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        39
        arrow-down
        2
        ·
        23 hours ago

        This attack must be run locally. The attacker must already have user access. They can then escalate privileges using this. Meaning your box must already be compromised for this to work. Still serious, but no need to panic in most cases.

          • ipp0@sopuli.xyz
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 hour ago

            Do you have a source for how often it happens or is this conjecture? I guess this would most often happen through supply chain attacks or physical access, the first not being all that common in my understanding and the latter not being a typical threat model for a home computer. But if you have a source explaining what actually happens, I would love to read it.

        • drkt@scribe.disroot.org
          link
          fedilink
          English
          arrow-up
          12
          arrow-down
          4
          ·
          22 hours ago

          /c/selfhosted moment

          Sure don’t patch a quiet and easy root shell escalation because it is, by itself, not a remote exploit. I sure do hope you trust every single piece of software running on your computer.

          • thesmokingman@programming.dev
            link
            fedilink
            English
            arrow-up
            14
            arrow-down
            3
            ·
            19 hours ago

            I think you’re displaying a very big gap between understanding risk assessment and understanding task completion. So far I have not seen anyone say they would not complete the task. I have seen people complete risk assessment. Risk assessment does not mean I will not do something, it just reflects the urgency with which I will do it. Most self-hosted users can safely apply basic risk assessment to see, while the impact may be high, the likelihood is low. Obviously the likelihood increases the more hands off you are with, say, unattended container updates for things that can escape containers or access the underlying system. Should most self-hosted users literally drop everything, rush home, and apply the patch? No, basic risk assessment does not merit that. Should everyone apply the patch? Yes.