CVE-2023-34359
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 · uneditedASUS RT-AX88U's httpd is subject to an unauthenticated DoS condition. A remote attacker can send a specially crafted request to the device which causes the httpd binary to crash within the "do_json_decode()" function of ej.c, resulting in a DoS condition.
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 confidenceThe ASUS RT-AX88U router's httpd service contains a vulnerability in the do_json_decode() function in ej.c. An unauthenticated remote attacker can send a specially crafted request that causes the httpd binary to crash, resulting in denial of service. The attack requires no authentication and is easily exploitable over the network.
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< 3.0.0.4.388.23748CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is ASUS RT-AX88UAccess the router web interface and check the model name in System Log or General Settings, or check the product label on the device itselfAffected if The device is not an ASUS RT-AX88U model
-
Check installed firmware versionLog into the router web interface, navigate to Administration > Firmware Upgrade, and note the displayed firmware version numberAffected if The firmware version is less than 3.0.0.4.388.23748 (e.g., 3.0.0.4.388.xxxxx with a lower build number)
-
Verify httpd service is accessibleAttempt to access the router's web management interface via HTTP or HTTPS from the network segment you want to test (e.g., curl http://router-ip/)Affected if The httpd service responds to requests, indicating it is running and reachable
A user is affected if they have an ASUS RT-AX88U router running firmware version lower than 3.0.0.4.388.23748 with the httpd web management interface accessible to the attacker.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.0.0.4.388.23748
Apply vendor firmware updates when available. As a temporary measure, restrict access to the router's web management interface from untrusted networks or disable remote management if not required.
ASUS RT-AX88U Firmware 3.0.0.4.388.23748 or later
- 1. Download firmware version 3.0.0.4.388.23748 or later from the official ASUS support website for the RT-AX88U model
- 2. Access the ASUS RT-AX88U router web administration interface via a browser
- 3. Log in with administrator credentials
- 4. Navigate to Administration > Firmware Upgrade
- 5. Click the 'Upload' button and select the downloaded firmware file
- 6. Wait for the firmware upload and installation to complete (do not power off the router)
- 7. Allow the router to reboot automatically
- 8. After reboot, verify the firmware version shows 3.0.0.4.388.23748 or higher in the router admin panel
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34359 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-34359 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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