CVE-2023-24167
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 · uneditedTenda AC18 V15.03.05.19 is vulnerable to Buffer Overflow via /goform/add_white_node.
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 confidenceBuffer overflow in Tenda AC18 router firmware V15.03.05.19 in the /goform/add_white_node endpoint allows remote attackers to execute arbitrary code via crafted input. The CVSS 9.8 indicates network-exploitable, low-attack-complexity vulnerability requiring no authentication.
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= 15.03.05.19CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 device modelLocate the router model number on the device label or check the web administration interface system information page. Confirm it is a Tenda AC18 model.Affected if The device is a Tenda AC18 router
-
Check the installed firmware versionAccess the router's web administration interface (typically at 192.168.0.1) and navigate to System Settings or Firmware Upgrade section to view the current firmware version. Alternatively, check the firmware file name if you have access to it.Affected if The firmware version is exactly 15.03.05.19
-
Verify the web management interface is accessibleAttempt to access the router's web interface from the network where the router is deployed. Check if HTTP/HTTPS ports 80 or 443 respond to requests.Affected if The router's web interface is reachable from untrusted networks (not just from trusted internal segments)
-
Confirm the /goform/add_white_node endpoint existsSend an HTTP GET or POST request to http://<router-ip>/goform/add_white_node and observe the response. A valid endpoint will return a response (even if error), while a non-existent endpoint may return 404.Affected if The /goform/add_white_node endpoint is accessible and responds to requests
You are affected if you have a Tenda AC18 router running firmware version 15.03.05.19 with the web management interface exposed to untrusted networks, as the unauthenticated add_white_node endpoint contains the buffer overflow vulnerability.
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 patch when available; until then, disable remote web management, restrict administrative interface to trusted networks, or place device behind a firewall.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24167 — 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-24167 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