dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2023-31889

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
An issue discovered in httpd in ASUS RT-AC51U with firmware version up to and including 3.0.0.4.380.8591 allows local attackers to cause a denial of service via crafted GET 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 · moderate confidence

A denial of service vulnerability exists in the httpd service of ASUS RT-AC51U routers running firmware version 3.0.0.4.380.8591 and earlier. A local attacker can send a specially crafted GET request to trigger the DoS condition.

MitigationApply the latest ASUS firmware update for the RT-AC51U when available, or implement network access controls to restrict local access to the httpd service.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 router model is RT-AC51U
    Log into the router web interface (typically 192.168.1.1) or check the device label/marketing box to verify the exact model number matches RT-AC51U
    Affected if The router is not an ASUS RT-AC51U model, then this specific CVE does not apply
  2. Check installed firmware version
    Access the router web admin interface, navigate to Administration or System status section, and locate the firmware version displayed. Compare it to 3.0.0.4.380.8591 - any version equal to or lower than this is affected
    Affected if Firmware version is 3.0.0.4.380.8591 or earlier
  3. Verify httpd service is running
    Access the router via telnet or SSH if enabled, and run a command to list running processes (such as 'ps' or similar) to confirm the httpd service is active
    Affected if The httpd process is not running, the vulnerability cannot be triggered even on affected firmware
  4. Check network accessibility of httpd service
    From a local host on the same network, attempt to access the router's web interface on the standard HTTP port 80 or HTTPS port 443 to confirm the service is reachable over the network
    Affected if The httpd service is accessible from the local network, an attacker on the same network could send the crafted GET request

You are affected if you own an ASUS RT-AC51U router running firmware version 3.0.0.4.380.8591 or earlier, with the httpd service running and accessible from your local network.

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 firmware update for the RT-AC51U when available, or implement network access controls to restrict local access to the httpd service.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31889 — 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-31889 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