You got me good for a couple seconds there lmao
Oh crap even my Atari 400 is done for! Yes, I mail in my responses here.
If you’re smart, like me, you’ll unplug your devices immediately. Failure to do so ensures your doom.
Okay. I briefly ate the onion, on this one. It tastes like sysadmin tears.
I had a msg to my team drafted before I realized I was a fucking idiot.
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.
Duct tape works a treat for that!
How is it in your defense when you were going to do it to them?
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
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)
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
Save it for April 1.
I was fooled until I saw the CVSS score of 11 on a scale of 0 to 10.
If you think that’s bad, this flaw is rated a 22.
I only figured it out because I read your comment.
That’s why I confessed. I’m glad to help.
I’m here cautiously making sure it’s a joke that I don’t understand. Problem exists between keyboard and seat.
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’m not taking any chances. I’ve already tossed
bashinto the/bin/Uh oh I tossed mine in sbin. What do?
quick, pull out your RAM and send it to me for diagnostics
Oh no we ve got Sam Altman on lemmy dot machine learning
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 directorySame 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
sudoprogram 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.That’s why there’s no
sudoon my system, onlydoas.sudo is so broken, automatic privilege cloning of any user
I work at google just shut off every server to protect us. 👍
I took the “us” in your statement to be “humanity” and it sparked an unexpected feeling of hope.
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
So zsh is good? /s
According to the report, zsh is even worse
2009 zsh adoption grows. Now the shell is also pretty, which researchers believe lures more victims.
nushell, ash, elvish, dash, powershell, …
powershell is good because no hacker can be bothered typing that much to get anything to work ;)
Security by utter absence of usability
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?”
pwsh
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, likelycat), so I’d still be careful 😬
Microsoft Paint: Not affected. Thank God.
Unless you have allowed the AI features to install
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.
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.
You should really place a /j somewhere before someone thinks they’re screwed
The community it’s posted in is a bit of a giveaway, isn’t it?
How dare you overestimate my intelligence.
I thought I was screwed
The fact that we think this is possible is a really good argument for slowing down and regulating tech. Like, this might happen tomorrow. We don’t fucking know.
Gotta minimize your attack surface sudo apt remove konsole for any Debian kde based distros
sudo apt remove apt sudoI used the stones to destroy the stones
While the palindromic structure of that command is pleasing to mine eye, LMDE basically called me a frickin’ idiot for trying.
I know it always asks
Continue [Y/n]and there’s noyes |orecho |to force that, so I was reasonably sure I’d get away with it, but I don’t think I could argue with the sentiment had it actually said that.(Also, I have Timeshift, so that would have saved my bacon but for the inconvenience of having to go through a rollback.)
Anyway, here’s what it said (scrolling may be required to see the last line which is clearly code for “you’re an idiot”):
REMOVING: apt apt-utils mint-meta-cinnamon mintsources mintupdate sudo apt-file command-not-found mint-meta-core mintsystem python3-repolib WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! apt Summary: Upgrading: 0, Installing: 0, Removing: 12, Not Upgrading: 1 Freed space: 52.3 MB Error: Removing essential system-critical packages is not permitted. This might break the system.First of all, it pleases me greatly that you appreciated the palindromic nature of it. That pleased me as I wrote it (you know how you can write something and realize that it’s unintentionally great? lol)
Second of all, it pleases me that you tried it. lol. I was originally a DOS/Windows guy, so while I know a tiny bit of the Deep Magic, it’s safe to say I’m a fairly average user on the Linux side of things, though I do love learning.
How brilliant. Just like with
rm / -rfprotection that you can override, but must override… I had actually assumed (without thought) thatsudoandaptwere built-in commands likedirandcdin DOS, so there wouldn’t be anything to remove. But makes sense that everything is a package.Today, thanks to you, I learned the most delightful thing. Thank you. <3
Everything is a package
I mean, pretty much. Or rather, everything is in a package. Back in the old days they were called source distributions or
.tar.gzs and you compiled everything yourself. Gentoo, for example, still does everything that way, but uses the name ‘package’ anyway.The
coreutilspackage, or something like it, contains multiple commands that a bare bones, command-line-only system would need, but some things are built into the shells. e.g.cdis always shell-based.echomay or may not be.ls(dir) is incoreutils.There are also things like
busyboxthat, in a single executable from a single package, contains a stripped-down version of everything in coreutils, a shell and a handful of other things too.
Honestly, I want to be allowed to break my system. I own it, it should do exactly what I say, warnings are fine, but software deciding it knows better than you is how we have reached the inescapable technogulag of the now.
You can, if you create an empty file at
/etc/apt/break-my-systemfirst. It’s intentionally not mentioned to prevent another Linus situationBecause of course you can.
I will say, in the world where you can’t do anything with “con:” or “prn:” or a few others in DOS, the fact that you CAN force Linux to let you completely and utterly fuck yourself if you truly want to… is great. lol
Wow, I thought you might be joking but this is real
In my experience, Linux only allows you to do 1 incredibly stupid thing at a time. Remove sudo? Cool. Remove apt? You betcha. Remove apt AND sudo? You’re fucking nuts, I ain’t doing that
https://www.gnu.org/philosophy/free-sw.en.html#four-freedoms
Freedom 0 says I can be nuts and that clankers better obey
You could always try using “sudo dpkg -r --force-all apt” instead. It won’t clean up the dependencies, admittedly.













