CVE-2023-39672
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 WH450 v1.0.0.18 was discovered to contain a buffer overflow via the function fgets.
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 buffer overflow vulnerability exists in Tenda WH450 router firmware v1.0.0.18 within the fgets function. The lack of proper bounds checking when fgets reads user-supplied input into a fixed-size buffer allows an attacker to overflow the buffer and potentially execute arbitrary code. With a CVSS 9.8 rating, this is likely exploitable remotely without 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= 1.0.0.18CVSS 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 router modelLog into the router web interface or check the device label to confirm the exact model is Tenda WH450 or WH450aAffected if The device model is not Tenda WH450 or WH450a, this specific CVE does not apply
-
Check the installed firmware versionAccess the router admin panel (typically at 192.168.0.1), navigate to System Settings or Firmware Upgrade section, and record the firmware version stringAffected if Firmware version is exactly 1.0.0.18 - this is the only affected version listed for this CVE
-
Verify the HTTP management interface is accessibleAttempt to reach the router's web interface from the network segment where the device is deployed - try accessing http://192.168.0.1 or the configured LAN IPAffected if The HTTP service is listening and responds, indicating the potentially vulnerable web component is active
-
Confirm remote WAN access is enabled (optional for remote exploitation)From an external network, attempt to reach the router's public IP on port 80/443 or check the router's WAN Management or Remote Management settings in the admin panelAffected if Remote management is enabled and the web interface is reachable from WAN, the vulnerability becomes remotely exploitable without authentication
The device is affected only if it is a Tenda WH450a running firmware version 1.0.0.18 with the HTTP management interface accessible (locally or remotely).
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 or device replacement. Disable remote management interfaces if not required.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39672 — 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-39672 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