CVE-2023-24169
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/FUN_0007343c.
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 vulnerability in Tenda AC18 router firmware V15.03.05.19 at the /goform/FUN_0007343c endpoint. The web interface form handler fails to properly validate input buffer sizes, allowing an attacker to overflow a fixed-length buffer and potentially execute arbitrary code with elevated privileges.
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 modelAccess the router admin interface or check the device label/marketing packaging to confirm it is a Tenda AC18 modelAffected if Device is not a Tenda AC18 router, then not affected by this specific CVE
-
Check the firmware versionLog into the router web interface, navigate to System Settings or Administration section, and locate the firmware version field. Alternatively, check via command line if telnet/ssh is enabled or examine the firmware binary fileAffected if Firmware version is 15.03.05.19 (exact match to affected version)
-
Verify the vulnerable endpoint existsAttempt to access the URI /goform/FUN_0007343c on the router's web server (http://[router-ip]/goform/FUN_0007343c). A 404 or 400 response confirms the endpoint exists; a 404 indicates the form handler may be presentAffected if The endpoint responds (not connection refused) indicating the web interface with this form handler is present
-
Check if remote web management is enabledIn the router web interface, go to Advanced Settings or Security settings and check if Remote Management or Web Access from WAN is enabled. Note the source IP restrictions if anyAffected if Remote management is enabled and accessible from untrusted networks, increasing exposure to remote exploitation
You are affected if you have a Tenda AC18 router running firmware version 15.03.05.19 with the web interface accessible (especially if remote management is enabled), as the buffer overflow exists in the /goform/FUN_0007343c form handler.
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 dataUpgrade to a patched firmware version if available; otherwise, disable remote management interfaces or restrict access to trusted IPs only until a fix is released.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24169 — 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-24169 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