Feeds

Be customers still exposed by router snafu

ISP playing cat and mouse on security

The Power of One eBook: Top reasons to choose HP BladeSystem

O2-owned ISP Be is fighting a constant battle to stay one step ahead of hackers because of a router vulnerability exposed back in February.

Be subscribers were exposed when London student Sid Karunaratne demonstrated it was possible to gain remote root access using poorly concealed telnet backdoors. Admin usernames and passwords had been left accessible by Be.

Details of the original exploit are here.

Be responded by first accusing Karunaratne of hacking its internal network, and then booting him off the service. It released a firmware update in March which tightened up the access control list for the telnet service ports.

However, it's emerged that whenever the router is reset to factory settings - which Be recommends as part of the procedure for switching from a dynamic to a static IP, for example - the configuration is refreshed with the original access control list, leaving it wide open once again. Customers sometimes restore factory settings when the router crashes too.

Routers sent out since the update don't have the vulnerability. Be says it addresses it in older models by flashing the firmware repeatedly everyday. It sent us this statement:

Access is restricted to specific IP addresses. This is managed through new firmware we released in March 2007. All new members that have joined since then have received Be Boxes with the updated firmware on. For all members that joined prior to that Be runs a script multiple times a day to update members firmware with the relevant patch.

It asked users to get in touch if they're having problems.

New O2 broadband customers, who will be using the Be ADSL2+ network, won't be affected by the constant need to flash the firmware*. ®

*Correction: Several readers wrote to point out our error that they are updating the ACL templates, not flashing the firmware. Apologies for the mistake.

Bootnote

Thanks to Finlay for the heads up.

Designing a Defense for Mobile Applications

More from The Register

next story
Mozilla fixes CRITICAL security holes in Firefox, urges v31 upgrade
Misc memory hazards 'could be exploited' - and guess what, one's a Javascript vuln
How long is too long to wait for a security fix?
Synology finally patches OpenSSL bugs in Trevor's NAS
Don't look, Snowden: Security biz chases Tails with zero-day flaws alert
Exodus vows not to sell secrets of whistleblower's favorite OS
Roll out the welcome mat to hackers and crackers
Security chap pens guide to bug bounty programs that won't fail like Yahoo!'s
HIDDEN packet sniffer spy tech in MILLIONS of iPhones, iPads – expert
Don't panic though – Apple's backdoor is not wide open to all, guru tells us
Researcher sat on critical IE bugs for THREE YEARS
VUPEN waited for Pwn2Own cash while IE's sandbox leaked
Four fake Google haxbots hit YOUR WEBSITE every day
Goog the perfect ruse to slip into SEO orfice
prev story

Whitepapers

Designing a Defense for Mobile Applications
Learn about the various considerations for defending mobile applications - from the application architecture itself to the myriad testing technologies.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Top 8 considerations to enable and simplify mobility
In this whitepaper learn how to successfully add mobile capabilities simply and cost effectively.
Seven Steps to Software Security
Seven practical steps you can begin to take today to secure your applications and prevent the damages a successful cyber-attack can cause.
Boost IT visibility and business value
How building a great service catalog relieves pressure points and demonstrates the value of IT service management.