Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalPublic exploit

Authentication Bypass in ASUS AiCloud Routers

IdentifiersCVE-2025-2492CWE-287

CVE-2025-2492 is a critical improper authentication vulnerability in the AiCloud functionality of ASUS routers. According to the provided content, the flaw can be triggered by a crafted request against routers with AiCloud enabled, allowing an unauthenticated remote attacker to bypass authentication controls and invoke unauthorized functions. Multiple sources in the content characterize the issue as an authentication bypass in AiCloud and note that successful exploitation can permit modification of router configuration and may enable follow-on arbitrary code execution or full device compromise, particularly on internet-exposed edge devices.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote unauthenticated attacker to execute unauthorized functions on the router. Based on the provided content, this can lead to unauthorized configuration changes, high-privilege control of the device, and potentially arbitrary code execution or full device takeover. In observed real-world activity, this vulnerability was reportedly exploited as part of Operation WrtHug to hijack vulnerable ASUS routers and repurpose them as persistent relay/proxy infrastructure.

Mitigation

If you can’t patch tonight, do this now.

If patching is not immediately possible, disable AiCloud to remove the exposed attack surface. The provided content also recommends disabling internet-facing and remote-access features where feasible, including WAN remote access, port forwarding, DDNS, VPN server, DMZ, port triggering, and FTP, especially on end-of-life devices. Strong, unique administrative and wireless passwords are additionally recommended, though they do not fully mitigate an authentication bypass flaw.

Remediation

Patch, then assume compromise.

Apply the latest ASUS firmware updates for affected routers immediately. The content indicates ASUS released updated firmware addressing CVE-2025-2492 and urges users to upgrade as quickly as possible. For unsupported or end-of-life devices that no longer receive fixes, replacement with a supported model is recommended.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
ASUS-AiCloud-RCEMaturityPoCVerified exploit

Repository contains a single substantive Go program, origasus.go, plus a README. The code is an operational exploit/scanner targeting ASUS AiCloud/AsusWRT devices and explicitly references a chained attack involving SETROOTCERTIFICATE to write /etc/cert.pem.1 and APPLYAPP/RC_SERVICE to execute commands. It is not merely a detector: it reads targets from stdin or a file, supports optional TLS and multi-port scanning, verifies ASUS-related indicators to reduce false positives, and then attempts exploitation using multiple HTTP request and shell-execution variants. The exploit is structured as a concurrent scanner with global configuration, signal handling, exploited-host tracking, and environment-driven loader customization. It maintains a list of common ASUS management ports, supports host:port parsing or separator-based input, and skips previously exploited hosts unless disabled. The payload logic is the most notable part: it builds several shell-script variants intended to be written to /etc/cert.pem.1, then tries many command-injection forms to execute that file. The staged script attempts to download kla.sh from a configurable loader host over HTTP or raw TCP using wget, busybox wget, curl, nc, or toybox nc, stores it in writable temp locations, marks it executable, and launches it in the background with a campaign tag. Fingerprintable observables include the default loader IP 11.11.11.11, HTTP path /bins/kla.sh, TCP port 3342, target-side file /etc/cert.pem.1, temp directories /dev/shm, /var/tmp, /tmp, and the local bookkeeping file exploited.txt. Overall, this repository is a compact standalone Go-based exploitation utility for mass-targeting vulnerable ASUS router/web-management interfaces, with built-in staging for a second-phase shell payload.

murrezDisclosed May 12, 2026gomarkdownwebnetwork
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware1

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity18

Community discussion across Reddit, Mastodon, and other social sources.