Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

11/29/2016
04:20 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

Deutsche Telekom Attacks Suggest Mirai Threat Poised To Become Much Larger

With attack, Mirai has added an exploit targeting Web service vulnerability.

A cyberattack that crippled Internet services for nearly one million customers of Deutsche Telekom earlier this week suggests that the threat posed by the Mirai IoT botnet malware is about to get a lot larger.

The attack is the first since Mirai surfaced in October that does not rely on weak and default passwords in routers, webcams, digital video recorders, and other so-called Internet of Things devices.

Instead it targeted a specific vulnerability in a management interface present in routers used by many customers of Deutsche Telekom with the goal of infecting the devices and making them part of a Mirai botnet. The infection attempts failed but nevertheless caused the routers to crash.

“Until now, Mirai just used weak passwords to exploit devices like routers. But with this version, it adds an exploit for a vulnerability in a web service,” says Johannes Ullrich, dean of research at the SANS Institute.

The kind of vulnerability that was exploited in the attack is very common, he says. “What we see right now is more or less just a tip of the iceberg. By adding this exploit, Mirai gained access to many more devices then it already had,” he said.

The disruptions for Deutsche Telekom customers started Sunday and continued through parts of early Monday. In all, about 900,000 customers, representing about 4% of the company’s 20 million fixed-line customers, were impacted in the attack, Deutsche Telekom said in a FAQ and alert on the incident.

By early Monday, the company had begun rolling out patches for the problem to affected customers. It advised customers to unplug their router for 30 seconds and then power the device back on for the update to take hold. It also offered a location where users could go to download the update manually and install it on their routers.

The fact that threat actors are attempting to distribute Mirai by exploiting software vulnerabilities in IoT devices is troubling, says Craig Young, security researcher at Tripwire.

“The most defining attribute is that this Mirai variant is propagating through a specific vulnerability rather than relying on poorly configured devices,” Young says. “The last wave of attacks would seek out devices with exposed Telnet or SSH management and attempt to guess passwords.”

Device owners could easily thwart such attacks by using a strong password or not directly exposing the management service to the Internet, Young says.

In contrast “this attack could not be blocked through any configuration change made by the end user,” Young says. “The management protocol being attacked is exposed in the device configuration required by various ISPs and is not one that consumers could disable,” on their own without a vendor-supplied patch, Young says.

In a SANS Internet Storm Center advisory, Ullrich identified the Deutsche Telekom routers that were attacked as originating from Acadyn, a Taiwanese modem manufacturer. But the vulnerable interface is present in other routers as well, including those from Zyxel, a maker of modems used by Irish ISP Eir, Ullrich said in the alert.

A count performed using the Shodan Internet scanning tool shows the total number of devices listening in on the port used by the management interface is as large as 40 million. But not all of them are likely to run the vulnerable implementations that were present in the Deutsche Telekom routers. “My personal "best guess" is that this vulnerability may have added 1-2 Million new bots to the Mirai botnet,” Ullrich wrote in the alert.

Related stories:

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Florida Town Pays $600K to Ransomware Operators
Curtis Franklin Jr., Senior Editor at Dark Reading,  6/20/2019
Pledges to Not Pay Ransomware Hit Reality
Robert Lemos, Contributing Writer,  6/21/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12960
PUBLISHED: 2019-06-25
LiveZilla Server before 8.0.1.1 is vulnerable to SQL Injection in functions.internal.build.inc.php via the parameter p_dt_s_d.
CVE-2019-12961
PUBLISHED: 2019-06-25
LiveZilla Server before 8.0.1.1 is vulnerable to CSV Injection in the Export Function.
CVE-2019-12962
PUBLISHED: 2019-06-25
LiveZilla Server before 8.0.1.1 is vulnerable to XSS in mobile/index.php via the Accept-Language HTTP header.
CVE-2019-12963
PUBLISHED: 2019-06-25
LiveZilla Server before 8.0.1.1 is vulnerable to XSS in the chat.php Create Ticket Action.
CVE-2019-12964
PUBLISHED: 2019-06-25
LiveZilla Server before 8.0.1.1 is vulnerable to XSS in the ticket.php Subject.