• in my defense, my team is always trying to be mr. achiever and drop the latest vulnerability. I got a glimpse of this one and got excited since I hadn’t heard of this “new named threat”. when I tried reading further to prepare my draft… the reach and exposure of this vulnerability became clear.

        also, to mitigate this, we’d have to hotpatch layer 8.

        • u shouldn’t play the achiever game with your team, it’s an exploitation tactic and it consumes every fiber of your being

          • my carcass has long been picked clean but I thought" hey maybe the old man still can find surprises those whippersnappers haven’t yet."… thinking “ohh lemmy stumbled upon something! beans!” (I think you have to say this when you reference lemmy now)

          • justifying my behavior because I was motivated by the aforementioned external behaviors by establishing their trends of beating me to the aforementioned punch.

            WOOO I need to let autocorrect hit that aforementioned word again yeah soo satisfying.

            • Nothing anyone else does demands you also do it. It is a mark of maturity to understand that if you don’t want something to happen, you should abstain because how you treat yourself is more important than how others do

      • I’ve sent a company wide email telling everyone I don’t want to be sysasmin anymore.

        It has nothing to do with the CVE

        • I’m here cautiously making sure it’s a joke that I don’t understand. Problem exists between keyboard and seat.

          • 12 days

            Not even that, it’s not a problem at all. They’re just saying that when you open a terminal program you get access to the shell. That is exactly the point of a terminal program. It’s a bit like “exclusive, shocking report: water is wet!”

            I mean, I guess part of the joke is if an attacker can get into your computer they can do nefarious things, but that’s not as funny.

  • Just tried it out. It is real. And really simple to do.

    Scary stuff. Tossing my machines in the bin tomorrow.

  • I just tested this exploit, I was easily able to remove the french language pack by typing “rm -fr /*”

    • Don’t forget the —no-preserve-root flag or you’ll get an index out of bounds when deleting the recipe for five-root-puree

      • This flag is fortunately not needed as /* ensures root recipes are preserved. It’s just that anything below isn’t.

        • Oh i was kind of going for the opposite. 😈

          BTW use caution with your glob there, that only does what you described if the folder has contents, if it doesn’t, rather than getting nothing you’ll get back the parent directory, at least in bash. I’m not one of the cool zsh kids.

          • Huh, are you sure or am I just stupid?

            [user@device Documents]$ mkdir test
            [user@device Documents]$ cd test
            [user@device test]$ ls ./*
            ls: cannot access './*': No such file or directory
            

            Same behavior with * instead of ./*.

            • I may be the stupid one, i’m sure there’s a related gotcha here under some condition, but objectively not the one i described. Sorry, did not intend to waste anyone’s time and i do appreciate the response back to set me straight.

  • Getting a shell is bad, but what makes this worse is the insecurity of popular Linux tools that can be used for privilege escalation.

    The sudo program has had a known vulnerability since its inception. The developers are incompetent. In some configurations, all you need is the user’s password and you can execute arbitrary code as root. Sometimes, no password is needed at all.

    • I took the “us” in your statement to be “humanity” and it sparked an unexpected feeling of hope.

  • 12 days

    Nobody show this to my boss please, they’ll be asking me why I haven’t fixed it yet

  • Phew! Just got done patching all my servers. The main IOCs are

    • C:\Windows\System32\cmd.exe
    • /bin/bash
    • /bin/sh
      • According to the report, zsh is even worse

        2009 zsh adoption grows. Now the shell is also pretty, which researchers believe lures more victims.

        • powershell is good because no hacker can be bothered typing that much to get anything to work ;)

          • 12 days

            I’m taking some admin/security courses and powershell was touted as “it’s so easy to make your own scripts to save time!”. I was just like, “the fuck Koolaid are you drinking?”

          • Was the command separated by dashes or case change? Let me che…ange to something else.

          • They have aliases for multiple commands (such as cd, ls, curl, likely cat), so I’d still be careful 😬

  • Holy shit, my computer is infected. I opened my terminal and typed “sudo ls -halR /” and it showed me every file on my computer. Oh my god.

  • 12 days

    Given simple primitives and runtime permissions, a skilled hacker can even bootstrap one of these “shells” from scratch, underlining the continued importance of banning math and computer science education in our schools.

  • You should really place a /j somewhere before someone thinks they’re screwed

  • 11 days

    I still find it funny that in the distant past an engineer thought pasted commands should have some ~~ characters added, so the user has to delete them & think about their actions while pressing their arrow or various faster ctrl+ keys …

  • Switch off computer is the best mitigation

    Removing keyboard and locking operator out of building is the next best thing.