[Adorapuff]

Also, this seems to affect more than bash, as the test code I posted worked on Fish.

[Eclipse]

You have a router in your house. If it's not a cheap piece of trash VxWorks router, you're vulnerable too.

Well then fuck. It's a D-Link running default firmware. I really need an upgrade...

---

EDIT: Nice addition to OP.

[Reiko]

Do you mean router or modem? Because my router connects to my modem which connects to the ISP from what I understand. DD-WRT is only accessible from my local net as I it is running on a router.

The router is making DHCP requests. A malicious or compromised ISP, or even a middleman, could exploit this bug through a crafted response to those.

[Dyme]

Here's the lame piece of shit I made yesterday when this was disclosed. Uses socat to listen for a chippy shell: http://goo.gl/3DHqgt

Spoiler:

[Reiko]

Here's the lame piece of shit I made yesterday when this was disclosed. Uses socat to listen for a chippy shell

Spoiler:

Change User-Agent to some random, arbitrary header so you have less chance of getting logged. Otherwise this looks good.

[Dyme]

Change User-Agent to some random, arbitrary header so you have less chance of getting logged. Otherwise this looks good.

Done.

[Reiko]

Aaaaand we're fucked

[Kizaru]

Aaaaand we're fucked
-snip-

Annnd im scared. Might as well not be on the internet for a while~

[Alan Turing]

Interesting thing, pretty fucked up.

[OldWolf]

there is a iptables patch here
http://cultofthedyingsun.wordpress.com/2...nort-rule/

###################DUMP###################
Initially (pre-patching bash), I thought of a possible way to mitigate this via an iptables rule, using the –string parameter, however, i haven’t fully tested it yet, but i think you’ll get the idea:

iptables -I INPUT -p tcp --dport 80 -m string --algo bm --string '() { :;};' -j DROP
I also wrote a quick snort rule to detect shellshock exploit attempts:
blah
###################DUMP###################