Almost 900,000 Deutsche Telekom customers were hit by network outages — an attack reportedly aimed at hijacking consumer routers, Reuters reported on Tuesday.
The attack, which began on Sunday and continued until Monday, rendered the victims without internet service over the weekend. According to Germany’s incumbent telco, this is the second such large-scale attack on the company’s internet-connected devices since late October.
Stephen Gates, chief research intelligence analyst at NSFOCUS, commented: “In many broadband networks, customer premise equipment (home/business routers) calls home to company headquarters to validate paying customers, and to periodically get configuration and software updates.
Take the systems offline that provide this service functionality to the routers, and the network can likely be impacted. Another possibility for the outage is that hackers uploaded malware to the update servers, and this malware was either pushed or pulled to thousands of routers. This is a perfect example of a denial of service outage that did not involve a targeted DDoS attack.
“Most people don’t know that all broadband service providers have ensured they have backdoors into ‘their’ customer-edge devices; which can be cable modems, DSL modems, routers, etc. The reason for this is simple.
It ensures people don’t get services for free, while at the same time allowing the provider access into the remote devices for troubleshooting, updating, billing, etc. This helps reduce truck rolls and the associated costs. In this case, it appears that hackers have figured out a way to capitalise on the backdoor, and cause a noteworthy denial of service outage.”
Synopsys’s Mike Ahmadi, global director – Critical Systems Security, said: “While it is still unclear what caused this mass outage, it is important to note that massively scalable cybersecurity attacks, as evidenced by the recent Mirai Botnet attacks, are sure to be the new rage with the malicious hacker community. This is particularly alarming because our testing tools have been able to uncover literally thousands of scalable attacks on very commonly deployed networking equipment and IoT devices over the last several years.
On more than one occasion we have discovered malformed inputs directed at the broadcast address of networks which caused the firmware of particular devices to erase, all at once. It seems that simply finding a vulnerability is no longer all that interests the malicious hacker world, but finding and exploiting high impact vulnerabilities is very interesting. Unless developers and users implement more rigour into discovering and mitigating software vulnerabilities, scalable attacks will continue to grow.”
A similar view is taken by Alex Mathews, EMEA technical manager at Positive Technologies. He added, “The attack of this kind isn’t something new: This year we had multiple reports about thousands of infected routers used for DDoS botnets. We would even suspect that this German story is about ‘a broken botnet’. After all, hackers are not very interested in broken routers, they prefer to take control over working routers, and use them for other attacks. Perhaps, someone tried to build a Mirai-like botnet out of these infected routers in Germany but something went wrong and routers just went off.
“Whether this attack could have been prevented depends on what type of vulnerability was used to infect the routers. For example, Mirai botnet code wasn’t too serious: the malware was looking for gadgets with well-known default passwords (admin: admin, root: password, and so on). If people had just changed these default passwords, their routers wouldn’t have been infected.
On the other hand, the malware authors can use more serious, unknown vulnerability in routers’ firmware or in communication protocols. In this case, users hardly can do anything to protect themselves. Only serious security tests can detect such vulnerability. It should be done by service providers and by routers’ manufacturers… but unfortunately, they don’t do enough safety testing.”
Comment on this article below or via Twitter: @IoTNow_ OR @jcIoTnow
