Why Am I Not Seeing Info On Asus Router Vulnerabilities Here?

[Elmer]

So, after stumbling across reports of Asus router vulnerabilities recently, I did a search for "port 53282" on this thread and found nothing. Asus has distributed this:

ASUS Official Statement on Recent Reports Regarding Router Security
2025/06/04

A blistering youtube concerning Asus can be found here: https://youtu.be/Vy_KWP04pfs

My concern is that I rely on this site to provide updates on exploits such as this and possible ways to make sure it hasn't happened on my Asus routers. I don't understand the silence.

 

[ColinTaylor]

Because this is "old news" that was discussed at the time.

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

Yet another one, or did we already know about this one? https://www.greynoise.io/blog/stealthy-backdoor-campaign-affecting-asus-routers

www.snbforums.com

 

[Viktor Jaep]

So, after stumbling across reports of Asus router vulnerabilities recently, I did a search for "port 53282" on this thread and found nothing. Asus has distributed this:

ASUS Official Statement on Recent Reports Regarding Router Security
2025/06/04

A blistering youtube concerning Asus can be found here: https://youtu.be/Vy_KWP04pfs

My concern is that I rely on this site to provide updates on exploits such as this and possible ways to make sure it hasn't happened on my Asus routers. I don't understand the silence.

This is an old CVE from 2023. It's been patched long ago. You can read more about it here:

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

Yet another one, or did we already know about this one? https://www.greynoise.io/blog/stealthy-backdoor-campaign-affecting-asus-routers

www.snbforums.com

 

[Elmer]

If it's old news, why the Asus vulnerability release of 2025/06/04, along with the customary shift of blame to the consumer with "change your password and make it longer and more complicated - oh okay."

 

[Viktor Jaep]

If it's old news, why the Asus vulnerability release of 2025/06/04, along with the customary shift of blame to the consumer with "change your password and make it longer and more complicated - oh okay."

Probably because Asus support is still getting calls from people 2 years later saying that their router is hacked, inaccessible, or the FBI has been calling them to let them know their router is participating in a DoS attack, meanwhile blaming Asus for all their problems. But the sad fact of the matter is that 99% of the home users out there probably aren't updating the firmware on their routers, or even know how to change their default router's admin password to something a bit more complex than "12345".

 

[ColinTaylor]

If it's old news, why the Asus vulnerability release of 2025/06/04, along with the customary shift of blame to the consumer with "change your password and make it longer and more complicated - oh okay."

You asked why this site hadn't reported it. It was reported and discussed back in May. That makes yesterday's GN video "old news".

 

[Viktor Jaep]

You asked why this site hadn't reported it. It was reported and discussed back in May. That makes yesterday's GN video "old news".

I think @RMerlin said it best:

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

Yet another one, or did we already know about this one? https://www.greynoise.io/blog/stealthy-backdoor-campaign-affecting-asus-routers

www.snbforums.com

 

[bennor]

I did a search for "port 53282" on this thread and found nothing. Asus has distributed this:

FYI, a search for "53282' does bring up an earlier (May 28, 2025) discussion on the vulnerability.
https://www.snbforums.com/threads/g...-thousands-of-asus-routers.94809/#post-957093

 

[OzarkEdge]

My concern is that I rely on this site to provide updates on exploits such as this and possible ways to make sure it hasn't happened on my Asus routers. I don't understand the silence.

'Silence' happens when members do not participate... do not volunteer to contribute to the crowd-sourced information here. Feel free to help out... break your silence.

OE

 

[RMerlin]

A blistering youtube

GamersNexus has turned into a Youtube version of British tabloids at this point, where stirring drama and ranting about unverified facts is more important, because of the views. I stopped watching a few years ago when he went through a rant that Asus would invalidate your motherboard warranty if flashing a beta BIOS, something that I personally knew not to be true. He visibly hadn't even asked them directly if that was the case. And a few days later, other tech media mentionned that they had contacted Asus to ask the question, and Asus told them that no, flashing a beta BIOS would not invalidate your warranty.

Real, professional journalism is dead in 2025. Bloggers have taken over the scene now.

updates on exploits such as this

Sigh... A botnet is NOT an exploit.

 

[Justinh]

I didn't know this open, non-ASUS run forum had the responsibility of divulging all ASUS security issues.

 

[Rhialto]

Haven't watched it all but I agree with GN that their Armory Crate thing is not welcome when you know computers a minimum. No idea if it's good for novices.

 

[Tech9]

I also would like to have information about new exploits right a way, with use examples if possible, but @RMerlin as someone who perhaps knows best what's going on doesn't want to cooperate for some strange reason. We usually find out about exploits only after they are patched and this is really disappointing...

 

[Viktor Jaep]

I also would like to have information about new exploits right a way, with use examples if possible, but @RMerlin as someone who perhaps knows best what's going on doesn't want to cooperate for some strange reason. We usually find out about exploits only after they are patched and this is really disappointing...

Like this?

CVE/asus/CVE-2023-39780/1/EN.md at main · D2y6p/CVE

CVE. Contribute to D2y6p/CVE development by creating an account on GitHub.

github.com

 

[Tech9]

Yes, but on time. Not after it was patched already. There is no fun when presented like this.

 

[RMerlin]

Yes, but on time. Not after it was patched already. There is no fun when presented like this.

CVE information almost always remain confidential until after they are patched. This is for obvious reasons. Early disclosure only occurs if the target is uncooperative in fixing the issue, or if the issue takes more than a specific amount of time to get fixed (typically 2 months).

This is simply how the industry works.

 

[Viktor Jaep]

Yes, but on time. Not after it was patched already. There is no fun when presented like this.

If you're looking for more fun on unpatched zero days, then you might want to hop on over to the dark web. I hear they're having all kinds of sales!

 

[Tech9]

This is simply how the industry works.

Obviously...

you might want to hop on over to the dark web

I'm good hacking your private WAN IP.

 

[Viktor Jaep]

I'm good hacking your private WAN IP.

Sadly, as you probably already know, I don't have any zero day exploits available on my private network.