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.

ABTV //

Vulnerability

11/30/2018
08:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

UPnProxy Still Infecting Thousands of Home & Small Business Routers

An analysis by Akamai finds that UPnProxy is still out in the wild and still targeting routers mainly used in homes and by small businesses.

UPnProxy is still out in the wild, and making security people's lives miserable.

Universal Plug and Play (UPnP) is a protocol designed to ease device and service discovery and configuration of consumer devices and networks. UPnProxy uses UPnP to rip open internal networks and expose them to external threats.

The technique, first described by Akamai in April, arises from incorrect implementations of UPnP affecting network segmentation across the WAN and LAN network interfaces in devices. Many of the affected devices are home routers.

In a blog published this week, Akamai found that 277,000 devices, out of a pool of 3.5 million, were running vulnerable implementations of UPnP. Further, the company's scanning showed at least 45,000 actively Network Address Translation (NAT) injected machines. These sets of injections, which affect the NAT tables, attempt to expose the TCP ports 139 and 445 on devices behind the router to the Internet.

These are the Server Message Block (SMB) ports of a Windows or Linux machine. The threat actors used these ports -- after the NAT injection -- to connect to systems that were behind the routers and were not supposed to be connected to the Internet. Akamai analysts cannot say for certain what was done with these connections. They are only able to see the injections, not the payloads that were delivered.

However, the researchers write that they "believe that someone is attempting to compromise millions of machines living behind the vulnerable routers by leveraging the EternalBlue and EternalRed exploits."

By logging the number of unique IPs exposed per router, they think that the confirmed injections expose a total of 1.7 million unique machines to the attackers.

The Eternal series of exploits were published by the Shadow Brokers after being stolen from the NSA. They use SMB ports for transversal. The Blue variant is for Windows, while the Red one targets Samba on Linux systems.

Akamai researchers think this is not a targeted attack, but more of a shotgun deal. It may be a way to get to systems that survived the first wave of Eternal attacks because they were hidden from the internet due to their NAT tables.

Compounding the problem is that administrators will have problems detecting the malicious NAT injections, as there is no administrative visibility into them on an injected router. This is due to the UPnP protocol itself, which hides all the details of forwarding that it does.

Admins will have to do something like scan an end-point and audit it's NAT table entries to get a handle on possible injections present.

Not fun.

Mitigation isn't simple either. Let's say admins get new routers that don't have the UPnP vulnerabilities that enable this type of abuse or that they ensure that UPnP is disabled if equipment is vulnerable. Disabling UPnP alone will not clear any NAT injections that have occurred.

To truly clear this up, the LAN traffic behind vulnerable routers will have to be carefully and deep-state monitored. Patching any possible affected systems with EternalBlue and EternalRed resistant versions is of course necessary.

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
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.