Tens of millions of network-enabled devices including routers, printers, media servers, IP cameras, smart TVs and more can be attacked over the Internet because of dangerous flaws in their implementation of the UPnP (Universal Plug and Play) protocol standard, security researchers from Rapid7 said Tuesday in a research paper.
Quote:
Eight remotely exploitable vulnerabilities have been identified in the Portable UPnP SDK, including two that can be used for remote code execution, the researchers said.
RT-N66U, RT-AC66U and other Asus routers are exposing SOAP to the internet according to this list.
Is Merlin's build vulnerable, and can you do a quick fix by updating to the newer versions of miniUPnP and UPnP?
The Following User Says Thank You to Bagman For This Useful Post:
Asuswrt still uses an older version of Miniupnpd (1.4, versus the 1.6 version used by Tomato). Tomato only upgraded theirs after Asuswrt had forked from them.
I started looking at upgrading miniupnpd, but my first attempt at going all the way to 1.7 didn't work too well (I need to upgrade it through patching, since Asuswrt's version is somewhat customized versus the original version, and the resulting patched tree would have many build issues).
I'll see into getting it upgraded for the next build 24 beta, so it can get good testing at the same time.
__________________
Asuswrt-Merlin: Customized firmware for Asus routers Github: github.com/RMerl - Twitter: RMerlinDev
See the sticky post for more info.
The Following 2 Users Say Thank You to RMerlin For This Useful Post:
I'll see into getting it upgraded for the next build 24 beta, so it can get good testing at the same time.
Thanks for looking into this Merlin. Now that all the info about these loopholes is out in the open, it seems like only a matter of time before they are targeted by worms/viruses. If you can upgrade the problem components and keep our routers secure, it's just another (major) reason why your firmware is better than the Asus firmware.
But does the miniUPnP issue mean it is vulnerable against external attacks or just attacks from the inside?
I thought external attacks would be prevented by sufficient iptables rules?
Read the article - external attacks because the default IPtables rules are not adequately implemented.
What annoys me is some of this stuff has been fixed for years, but big companies like Asus (who should know better) are still using code from 2008. All the have to do is update the relevant modules with ones that are now available.
The Following User Says Thank You to Bagman For This Useful Post:
Read the article - external attacks because the default IPtables rules are not adequately implemented.
What annoys me is some of this stuff has been fixed for years, but big companies like Asus (who should know better) are still using code from 2008. All the have to do is update the relevant modules with ones that are now available.
At this point, it's unsure if Asuswrt is vulnerable or not. While Asus runs an older miniupnpd, they tend to regularily backport security fixes from upstream, so it's possible they might have patched that flaw already.
Again: unless someone actually test it, it's unsure if it's vunlerable or not. I just want to play it safe on my end, and try to get miniupnpd upgraded to at least version 1.6 (I'll port the Tomato version if needs be, since I don't think Asus has done many changes since the original fork from Tomato).
__________________
Asuswrt-Merlin: Customized firmware for Asus routers Github: github.com/RMerl - Twitter: RMerlinDev
See the sticky post for more info.
At this point, it's unsure if Asuswrt is vulnerable or not. While Asus runs an older miniupnpd, they tend to regularily backport security fixes from upstream, so it's possible they might have patched that flaw already.
Whether miniupnpd itself is vulnerable or not I'm not sure yet, but it doesn't appear that Asuswrt exposes miniupnpd to the WAN interface (some probing from an external server using nmap shows no responses to my attempts). Even if miniupnpd were vulnerable to such attacks, they would definitely require access to the internal LAN to start, and if you have access to the internal LAN, why would you need to exploit miniupnpd.
This post also seems to indicate that Asus has patched miniupnpd to fix these vulnerabilities.
I just installed Java and the Rapid 7 scan test. It identifies my RT-N66U running the latest Merlin beta as a UPnP device, but says it's not exploitable. I get the same results as KevTech does in the link in the post above.
Maybe Asus has patched the vulnerability even though they've patched to the older UPnP 1 that is listed as vulnerable?
UPNP Security flaw.
Linear Mode
