Earlier quoted context omitted.
While they sit there, oblivious to the fact that that router thing we use for the interwebs and all those IP cameras, NAS devices, and switches in their office are running linux, and bash, and are about to be used for industrial-grade extortion.
It's unlikely many consumer routers would be running Bash. They'd more likely have Busybox with the bog standard Bourne Shell. And same goes for most other embedded Linux devices too. Though I'm not suggesting that one shouldn't check their own devices to be safe rather than sure.
Shellshock DHCP Remote Code Execution – Proof of Concept
91–100 of 160 posts
Re: Shellshock DHCP Remote Code Execution – Proof of Concept
#92dhcp-option-force=114,() { :; }; if hash apt-get 2>/dev/null; then apt-get update -y && apt-get upgrade -y;fi; if hash yum 2>/dev/null; then yum update;fi;
to upgrade most vulnerable systems that connect to our network :) What other upgrade commands are there?
Re: Shellshock DHCP Remote Code Execution – Proof of Concept
#93So now we can have dhcp-option-force=114,() { :; }; if hash apt-get 2>/dev/null; then apt-get update -y && apt-get upgrade -y;fi; if hash yum 2>/dev/null; then yum update;fi; to upgrade most vulnerable systems that connect to our network :) What other upgrade commands are there?
Re: Shellshock DHCP Remote Code Execution – Proof of Concept
#94Earlier quoted context omitted.
It's unlikely many consumer routers would be running Bash. They'd more likely have Busybox with the bog standard Bourne Shell. And same goes for most other embedded Linux devices too. Though I'm not suggesting that one shouldn't check their own devices to be safe rather than sure.
And "indusrial" routers are not running bash, or linux for that matter, either.
However in all cases, I think you'd still be right about Bash not being present.
Re: Shellshock DHCP Remote Code Execution – Proof of Concept
#95Re: Shellshock DHCP Remote Code Execution – Proof of Concept
#96Why did the quotes show up?
Re: Shellshock DHCP Remote Code Execution – Proof of Concept
#97Minimalism is seriously a good idea. "Features" are not harmless and cost way more than you think. Providing more flexibility or functionality than absolutely necessary should really be considered and called out as defective, smelly and a bad practice.
Re: Shellshock DHCP Remote Code Execution – Proof of Concept
#98Is it just me or would it be a good time to learn a bigger lesson from Heartbleed and Shellshock: Minimalism is seriously a good idea. "Features" are not harmless and cost way more than you think. Providing more flexibility or functionality than absolutely necessary should really be considered and called out as defective, smelly and a bad practice.
Re: Shellshock DHCP Remote Code Execution – Proof of Concept
#99Earlier quoted context omitted.
Assuming it's a network full of machines who haven't bothered updating yet. EDIT: right?
Um, "haven't bothered"? Think about all the Linux/Unix -based devices that could be affected here, it's in the millions. Do you run a local server on your box? How about your Linux-based router? Has it been patched yet? Why not, it's been more than 24 hours now.
In the embedded world, people rarely run full GNU userland utils. They're extremely big and bloated, and embedded devicse needs maximum bang for buck. Therefore most of them comes with busybox, which besides being incredibly compact also is 100% unaffected.
Same goes for Android/Linux-based phones. Most don't come with a proper shell at all, and those who do, usually have busybox.
Re: Shellshock DHCP Remote Code Execution – Proof of Concept
#100Is it just me or would it be a good time to learn a bigger lesson from Heartbleed and Shellshock: Minimalism is seriously a good idea. "Features" are not harmless and cost way more than you think. Providing more flexibility or functionality than absolutely necessary should really be considered and called out as defective, smelly and a bad practice.
Which brings to mind the latest push for systemd as an init replacement. :/