dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 23 Jun 2025.
Rt Ax55 FirmwareOperating system · Asus

CVE-2023-39780

HIGH · 8.8 CVSS v3.1 Published 2023-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild Public exploit 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
On ASUS RT-AX55 3.0.0.4.386.51598 devices, authenticated attackers can perform OS command injection via the /start_apply.htm qos_bw_rulelist parameter. NOTE: for the similar "token-generated module" issue, see CVE-2023-41345; for the similar "token-refresh module" issue, see CVE-2023-41346; for the similar "check token module" issue, see CVE-2023-41347; and for the similar "code-authentication module" issue, see CVE-2023-41348.

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

OS command injection vulnerability in ASUS RT-AX55 firmware 3.0.0.4.386.51598 allows authenticated attackers to execute arbitrary OS commands by injecting them into the qos_bw_rulelist parameter of the /start_apply.htm endpoint.

MitigationApply vendor firmware updates when available; if no patch exists, restrict access to the router's web management interface to trusted users only via network segmentation or VPN.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rt Ax55 FirmwareOperating system
Affected:= 3.0.0.4.386.51598

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. Confirm the device model
    Access the router web interface or check the device label to verify it is an ASUS RT-AX55 router.
    Affected if The device is not an ASUS RT-AX55.
  2. Check the firmware version
    Log into the router web interface, navigate to Administration > Firmware Upgrade or similar, and note the installed firmware version. Compare against 3.0.0.4.386.51598.
    Affected if The installed firmware version is exactly 3.0.0.4.386.51598.
  3. Verify QoS bandwidth rule configuration access
    Navigate to the QoS (Quality of Service) settings in the router web interface and locate the bandwidth rule configuration section where qos_bw_rulelist parameter would be used.
    Affected if The QoS bandwidth rule configuration feature is accessible and exposed.
  4. Check web management interface accessibility
    Determine if the router web management interface (port 80/443) is accessible from untrusted networks or the internet.
    Affected if The management interface is exposed to untrusted networks.

A user is affected if they are running firmware version 3.0.0.4.386.51598 on an ASUS RT-AX55 router with the QoS bandwidth rule feature accessible to authenticated users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available; if no patch exists, restrict access to the router's web management interface to trusted users only via network segmentation or VPN.

Recommended fix Moderate confidence

ASUS RT-AX55 latest available firmware (check official ASUS support for most recent version)

  1. 1. Log into the ASUS RT-AX55 router administration interface at http://192.168.1.1
  2. 2. Navigate to 'Administration' > 'Firmware Upgrade'
  3. 3. Click 'Check for Update' to see if a newer firmware version is available
  4. 4. If an update is available, download and install it
  5. 5. Alternatively, visit the official ASUS support site at https://www.asus.com/supportonly/rt-ax55/helpdesk_download/ and manually download the latest firmware version
  6. 6. Upload the firmware file through the web interface and wait for the update to complete
  7. 7. After the router reboots, verify the new firmware version in the administration panel
Caveat Router firmware updates may reset some configuration settings; back up configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rt Ax55 Firmware Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2023-39780 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