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.

Endpoint Security

12/21/2018
08:15 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Huawei Routers Vulnerable to Simplified Credential Stuffing Attack

Security researchers at NewSky have found a vulnerability in Huawei's HG routers that leave these devices open to a brute force attack. The company has been notified, but it's not clear what, if any fix, has been applied.

Huawei has found itself in the news a lot as of late. There's been the falling out of favor with the US government over espionage concerns, and the company's CFO has been detained in Vancouver by Canadian authorities at the request of the Justice Department.

And now things are worse.

Ankit Anubhav, a principal researcher at NewSky Security, noted a massive security problem involving Huawei HG routers in the company's blog. This is a demonstrable fault -- not one simply based on suspicion of the company's motives.

Over the course of 2018, routers have been a specific target for attackers, including CVE-2018-14847 (Mikrotik) and CVE-2014-8361. These are prime example of how these devices can be abused as a stepping stone for cyber attacks.

However, a standard kind of credential stuffing attack is usually based on the "spray-and-pray" technique -- meaning that the actor will attack any reachable device whether it has default credentials or not, while trying determine if those default credentials will allow them to hijack the device.

CVE-2018–7900 simplifies this entire way of doing things. NewSky found that Huawei's router panel will leak this information if one knows what to look for when targeted by an attacker.

NewSky notes: "When someone has a look on the html source code of login page, few variables are declared. One of the variables contain a specific value. By monitoring this specific value, one can come to the conclusion that the device has the default password."

So, by simply looking for the presence of this specific value, the vulnerability can be detected. It is a string that can be scanned for by using a utility like Shodan or ZoomEye.

This give an attacker some important advantages. First, the attacker does not need to directly scan the Internet for finding the vulnerable devices. Such a scan may lead investigators back to them.

Also, there is now no need to attempt a failed login to determine if the device is vulnerable. Attackers using this technique also do not have the likelihood of encountering a generic honeypot, which will not have this flag.

NewSky has not revealed the actual string involved in this potential attack. In the company blog, researchers note: "The exact variable, proof of concept details and images explaining the vulnerability" will not be shared.

This may be due to Huawei trying to rectify the situation. NewSky claims it contacted the company about this particular security problem at the end of September.

In November, Huawei announced that it has provided a fix but is working with carrier operators for complete resolution. It is unclear what exactly that means.

In its announcement, the company noted that "Huawei has finished the investigation and confirmed that Huawei HG product is affected by this vulnerability. Huawei has already provided a version to fix the vulnerability and has contacted the affected carrier."

That's all well and good, but it's been well established over the years that there is no security gained from simply hiding the vulnerability as is now the case.

Some attacker will undoubtedly find the magic string to search for and use it. Fix it, Huawei -- don't just hide it.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/17/2020
Cybersecurity Bounces Back, but Talent Still Absent
Simone Petrella, Chief Executive Officer, CyberVista,  9/16/2020
Meet the Computer Scientist Who Helped Push for Paper Ballots
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-25789
PUBLISHED: 2020-09-19
An issue was discovered in Tiny Tiny RSS (aka tt-rss) before 2020-09-16. The cached_url feature mishandles JavaScript inside an SVG document.
CVE-2020-25790
PUBLISHED: 2020-09-19
** DISPUTED ** Typesetter CMS 5.x through 5.1 allows admins to upload and execute arbitrary PHP code via a .php file inside a ZIP archive. NOTE: the vendor disputes the significance of this report because "admins are considered trustworthy"; however, the behavior "contradicts our secu...
CVE-2020-25791
PUBLISHED: 2020-09-19
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with unit().
CVE-2020-25792
PUBLISHED: 2020-09-19
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with pair().
CVE-2020-25793
PUBLISHED: 2020-09-19
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with From<InlineArray<A, T>>.