CVE-2024-35388
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 · uneditedTOTOLINK NR1800X v9.1.0u.6681_B20230703 was discovered to contain a stack overflow via the password parameter in the function urldecode
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 confidenceA stack buffer overflow vulnerability exists in TOTOLINK NR1800X router firmware v9.1.0u.6681_B20230703. The vulnerability is located in the urldecode function, where the password parameter from HTTP requests is processed without proper bounds checking, allowing an attacker to overflow the stack buffer and potentially execute arbitrary code.
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= 9.1.0u.6681_b20230703CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the firmware version of the TOTOLINK NR1800X deviceLog into the router web management interface and navigate to System Status or Firmware Version settings to view the installed firmware version. Alternatively, use the router's command line (via UART/serial or SSH if enabled) and run: cat /proc/version or check /etc/versionAffected if The displayed firmware version is exactly 9.1.0u.6681_B20230703
-
Verify the web management interface is accessibleAttempt to access the router's web interface by entering the device's IP address in a web browser. Confirm the login page loads successfully.Affected if The web management interface is reachable on the network (even if authentication is required, the interface is exposed)
-
Check for the urldecode function exposure in HTTP processingUsing a web proxy or curl, send an HTTP request to the router's login endpoint with an abnormally long string in the password parameter (e.g., 500+ characters). Observe if the device crashes, becomes unresponsive, or if there is no length validation error returned.Affected if The device accepts an excessively long password parameter without rejecting it or truncating, indicating missing bounds checking
You are affected if your TOTOLINK NR1800X is running firmware version 9.1.0u.6681_B20230703 and the web management interface is network-accessible.
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.
From vendor dataApply vendor firmware updates when available; if no patch exists, consider network segmentation to limit exposure to the device's web management interface and disable remote administration if possible.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35388 — 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-2024-35388 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