Spark (or actually telecom) provided routers vulnerable to Shellshock?

Forums › Spark New Zealand › Spark (or actually telecom) provided routers vulnerable to Shellshock?

jacwlg

43 posts

Geek
+1 received by user: 8

Topic # 153472 27-Sep-2014 22:24

I have a ONT and a router provided by telecom for my fibre connection, are they vulnerable to the Shellshock bug?

I couldn't find any information on Spark's website.

wasabi2k

2091 posts

Uber Geek
+1 received by user: 848

Reply # 1142883 28-Sep-2014 09:28

One person supports this post

Are either actually accessible to the internet?

You need a process that is internet accessible (apache etc) for it to actually be an issue externally.

jacwlg

43 posts

Geek
+1 received by user: 8

Reply # 1142884 28-Sep-2014 09:32

wasabi2k: Are either actually accessible to the internet?

You need a process that is internet accessible (apache etc) for it to actually be an issue externally.

i don't run web servers or anything but I do run things like BitTorrent and have configured port forwarding on the router, does that matter?

freitasm

BDFL - Memuneh
61189 posts

Uber Geek
+1 received by user: 11971

Administrator

Trusted

Geekzone

Lifetime subscriber

Reply # 1142885 28-Sep-2014 09:42

One person supports this post

He's asking if those processes run on the modem/router itself.

Backblaze cloud backup (personal and business) | Geekzone broadband switch | Amazon (Geekzone aff) | MightyApe (Geekzone aff) |

My technology disclosure | Business Transformation | Enterprise Content Management | Customer Relationship Management

jacwlg

43 posts

Geek
+1 received by user: 8

Reply # 1142887 28-Sep-2014 09:46

freitasm: He's asking if those processes run on the modem/router itself.

thanks.

No, the BT client runs on a Windows machine, the router only does port forwarding.

eXDee

4025 posts

Uber Geek
+1 received by user: 1076

Trusted

Reply # 1142926 28-Sep-2014 12:35

One person supports this post

My Guess: Probably not. Most embedded devices in the modem/router category don't tend to run full bash, they tend to run busybox due to its small footprint.
Of course there are exceptions to this, which is why this bug is a problem even for embedded devices.

If you can get a telnet or ssh session open, use bash --version or echo $BASH_VERSION to see if you have it

raytaylor

3224 posts

Uber Geek
+1 received by user: 624

Trusted

Reply # 1143005 28-Sep-2014 16:11

2 people support this post

I'd be more worried about the dynalink routers that a certain ~4th largest ISP in the country was sending out to customers for about 5 years with admin/admin credentials and the port 80 web admin accessible on the WAN interface, with the DSL username and password in plaintext on the ppp settings page sourcecode.

Ray Taylor
Taylor Broadband (rural hawkes bay)
www.ruralkiwi.com

There is no place like localhost
For my general guide to extending your wireless network Click Here

hio77

'That VDSL Cat'
8446 posts

Uber Geek
+1 received by user: 1816

Trusted

Spark

Subscriber

Reply # 1143006 28-Sep-2014 16:13

raytaylor: I'd be more worried about the dynalink routers that a certain ~4th largest ISP in the country was sending out to customers for about 5 years with admin/admin credentials and the port 80 web admin accessible on the WAN interface, with the DSL username and password in plaintext on the ppp settings page sourcecode.

dlinks were bad for this too :/

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

jacwlg

43 posts

Geek
+1 received by user: 8

Reply # 1143174 28-Sep-2014 22:07

eXDee: My Guess: Probably not. Most embedded devices in the modem/router category don't tend to run full bash, they tend to run busybox due to its small footprint.
Of course there are exceptions to this, which is why this bug is a problem even for embedded devices.

If you can get a telnet or ssh session open, use bash --version or echo $BASH_VERSION to see if you have it

thanks for he information.

I didn't have luck getting telnet or ssh to work, I can get a telnet session but the user/password from the web interface doesn't work for telnet, ssh doesn't even connect.