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

Arbitrary Command Execution in ASUS Router AiCloud

IdentifiersCVE-2024-12912CWE-77· Improper Neutralization of Special…

CVE-2024-12912 is an improper input insertion vulnerability in ASUS Router AiCloud on certain router models that can lead to arbitrary command execution. The provided content states that the flaw affects the AiCloud remote access feature and is exploitable via remote access through AiCloud. Reporting on Operation WrtHug indicates attackers leveraged this issue against outdated or end-of-life ASUS WRT routers as part of intrusion chains targeting AiCloud-exposed devices. Specific vulnerable functions or code paths are not provided in the supplied content, but the issue is characterized as a command-execution flaw caused by unsafe insertion of attacker-controlled input.

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 can allow an attacker to execute arbitrary commands on the affected router, resulting in high-privilege control of the device. In the observed campaign context, such access was used to install persistent SSH backdoors, maintain long-lived control across reboots and in some cases firmware updates, and repurpose compromised routers as encrypted relay or proxy nodes for malicious traffic and botnet-style infrastructure.

Mitigation

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

If immediate patching or replacement is not possible, disable AiCloud and other internet-facing remote access features to remove exposure. ASUS guidance in the provided content also recommends disabling WAN remote access, port forwarding, DDNS, VPN server, DMZ, port triggering, and FTP where not required, and monitoring for unusual network activity or indicators of compromise such as unexpected AiCloud TLS certificates or unauthorized SSH access.

Remediation

Patch, then assume compromise.

Apply the ASUS firmware updates that address CVE-2024-12912, as referenced in the ASUS Security Advisory section dated 01/02/2025 for the AiCloud vulnerability. Upgrade affected routers to the latest supported firmware. For unsupported or end-of-life devices that no longer receive fixes, replace them with supported models.
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 activity3

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