What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

“GreyNoise Discovers Stealthy Backdoor Campaign Affecting Thousands of ASUS Routers”

XIII

Very Senior Member
Yet another one, or did we already know about this one?

 
This article is about the malware itself, not about a new security issue. That malware is getting installed through brute forcing of the login, or through old security issues (one of them going back to 2023 - long fixed).
 
New report of an old CVE - good reminder that devices that are End of Support should be replaced sooner than later...
 
This seems to be blowing up! Have seen a couple of news articles that picked up on GreyNoise article.
The sky is falling......
 
And once again people fail to understand what they read (assuming they actually READ the article and nost just the clickbait titles of news reports), and just get hit by the sensationalism behind it. So tired of this constantly repeating itself.
 
RMerlin's comment from the other snbforums discussion in case people are not clicking on the link and reading the other discussion comments:
This article is about the malware itself, not about a new security issue. That malware is getting installed through brute forcing of the login, or through old security issues (one of them going back to 2023 - long fixed).
 
In summary, we are observing an ongoing wave of exploitation targeting ASUS routers, combining both old and new attack methods. After an initial wave of generic brute-force attacks targeting login.cgi, we observe subsequent attempts exploiting older authentication bypass vulnerabilities. Using either of the above methods to gain privileged access to ASUS hardware, we observe payloads exploiting a command injection vulnerability to create an empty file at /tmp/BWSQL_LOG. This existence of a file at this path enables BWDPI logging, a TrendMicro feature embedded in ASUS routers.

Finally, we see remote SSH enabled on a high port TCP/53282 through the official ASUS settings with an attacker controlled public key added to the router’s keyring. This grants the attacker exclusive SSH access. Additionally, because the backdoor is part of the official ASUS settings, it will persist across firmware upgrades, even after the original vulnerability used to gain access has been patched.
 
The sky is falling!
One router model. Firmware patched long ago...
 
Last edited:
Was there any comms from ASUS that routers needed to be wiped after the update that patched these issues?
 
Last edited:
Pulled from another Forum:

It's an authentication bypass that Asus are responsible for, chained to a patched CVE which then provides persistent SSH access. Asus's firmware updates don't remove the SSH changes, and as far as I can tell there has been no mass communication from their side of "patch your router and then factory default it", so it's totally fair to lay the blame with Asus. One of the models is the RT-AX55 (https://www.asus.com/networking-iot...ries/rt-ax55/helpdesk_bios?model2Name=RT-AX55), where's the notice that there's a problem with it and it needs defaulting? There's no mention of any critical security flaws that have been resolved in the change log, so how are users meant to know about them? The technical writeup contains a review of some of the code that Asus are curling out, and it contains:

Authors Note: While not directly relevant to our current investigation, --no-check-certificate on the wget command means that your Google OAuth token is sent to a remote server without validating the SSL/TLS certificate. This has implications.

This is most likely because they don't want it to fail when the clock is set incorrectly because they are too lazy to handle that condition and suggest that the user might want to check the time, but it means that anyone can MITM the OAuth token because the router will just ignore cert errors. This stuff doesn't happen in a professional development environment, but it absolutely happens when people throw any old crap together until it compiles without errors and then ships it.
 
The sky is falling!
One router model. Firmware patched long ago...

The vulnerability appears to impact multiple models of routers from ASUS, such as the RT-AX55, RT-AX59U, RT-AX86 and many more. But we haven’t yet found a full and confirmed list.

However, the bad news is that the attacker’s SSH configuration changes are NOT removed by firmware upgrades. Put another way, if a router was compromised before updating, the backdoor will still be present unless SSH access is explicitly reviewed and removed.
 

The vulnerability appears to impact multiple models of routers from ASUS, such as the RT-AX55, RT-AX59U, RT-AX86 and many more. But we haven’t yet found a full and confirmed list.

However, the bad news is that the attacker’s SSH configuration changes are NOT removed by firmware upgrades. Put another way, if a router was compromised before updating, the backdoor will still be present unless SSH access is explicitly reviewed and removed.
This is not an epidemic but another case of the "news" media flogging something to death to "sell" copy. At the worse this is limited to un-patched routers. Somewhere I saw an estimate of five to six thousand routers of one model number. The regulars here have nothing to worry about. The owners of the vulnerable/infected routers have no clue that they needed to do updates (My guess is this is over 90% of home users). There is nothing we can do for those poor souls. We need to keep our own home and business networks save and updated. Yes, talking network security is a good thing but those 90% just do not care. Spend some time in a cell phone store, a Best Buy or Staples and you will be amazed at the ignorance of people who use these high tech products!
 
However, the bad news is that the attacker’s SSH configuration changes are NOT removed by firmware upgrades
No malware is ever removed by a firmware upgrade. Just like viruses won't disappear from a Windows PC just becaue you install a Windows update. You still need to clean it up. In the case of a router, that means doing a factory default reset. Nothing unusual there.
 
Running Skynet with securemode enabled (the default) would have also disabled SSH WAN access once you were infected.
 
This article is about the malware itself, not about a new security issue. That malware is getting installed through brute forcing of the login, or through old security issues (one of them going back to 2023 - long fixed).
Hi ...
May someone please confirm if the patch for CVE-2023-39780 is included in the 386.14.2 firmware version ?
The article refers other vulnerabilities without CVE # assigned. Is there any info on those ?
Thank you.
 
Last edited:

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top