OS Command InjectionWeakness · CWE-78

CVE-2024-1655

HIGH · 8.8 CVSS v3.1 Published 2024-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Certain ASUS WiFi routers models has an OS Command Injection vulnerability, allowing an authenticated remote attacker to execute arbitrary system commands by sending a specially crafted request.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ASUS WiFi routers contain an OS Command Injection vulnerability allowing authenticated remote attackers to execute arbitrary system commands via specially crafted HTTP requests. The vulnerability stems from insufficient input validation in the router's web management interface, enabling attackers with valid credentials to bypass sanitization and inject OS commands.

MitigationApply the latest ASUS router firmware update from the vendor's support portal immediately. If no patch is available, restrict administrative interface access to trusted IP addresses only and change default credentials to reduce the attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ASUS router model and firmware version
    Log into the router web管理界面 (usually at 192.168.1.1) and navigate to Administration > Firmware Upgrade or Advanced Settings > System to view the model number and current firmware version. Alternatively, check the sticker on the router device itself.
    Affected if The device is an ASUS WiFi router and the firmware version falls within the affected version ranges (obtain specific ranges from ASUS security advisory for this CVE).
  2. Verify if remote web management is enabled
    Log into the router web界面 and navigate to Advanced Settings > Administration > Remote Access Configuration. Look for settings such as 'Enable Web GUI from WAN', 'Enable SSH', or 'Allow remote management' and confirm whether they are turned ON.
    Affected if Remote access to the web management interface (WAN access) is enabled, making the command injection vulnerability remotely exploitable.
  3. Confirm authentication requirements are enforced
    Check that strong, non-default administrator passwords are configured. Navigate to Administration > System Settings > Router Account or similar, and verify the admin password has been changed from the manufacturer default.
    Affected if Default credentials remain in use, allowing authenticated attackers (or attackers who guess defaults) to exploit the vulnerability.
  4. Inspect router for signs of unauthorized command execution
    Check router system logs (Administration > System Log) for unexpected commands, shell invocations, or suspicious HTTP requests. Look for entries containing shell metacharacters (;, |, &, `, $()) or unfamiliar processes.
    Affected if Logs show evidence of injected commands, unexpected shell executions, or suspicious HTTP parameter patterns that bypass input validation.

You are affected if you run an ASUS WiFi router with a vulnerable firmware version AND the remote web management interface is accessible from WAN, especially if default credentials are still in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest ASUS router firmware update from the vendor's support portal immediately. If no patch is available, restrict administrative interface access to trusted IP addresses only and change default credentials to reduce the attack surface.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1655 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1655 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data