CVE-2024-3874
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 · uneditedA vulnerability was found in Tenda W20E 15.11.0.6. It has been declared as critical. This vulnerability affects the function formSetRemoteWebManage of the file /goform/SetRemoteWebManage. The manipulation of the argument remoteIP leads to stack-based buffer overflow. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-260908. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA stack-based buffer overflow vulnerability exists in Tenda W20E firmware 15.11.0.6 within the formSetRemoteWebManage function in /goform/SetRemoteWebManage. The remoteIP parameter is not properly bounds-checked before being copied to a stack-allocated buffer, allowing an attacker to overwrite adjacent memory by sending an oversized IP address value. This can potentially allow remote code execution on the affected device.
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.11.0.6CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm device model is Tenda W20EAccess the device administrative interface or check the device label/marketing materials to verify the model number is W20EAffected if The device is not a Tenda W20E model
-
Verify firmware version is 15.11.0.6Log into the Tenda W20E admin panel, navigate to System Settings or Firmware Upgrade page, and check the displayed firmware version. Alternatively, use the Tenda firmware upgrade page or telnet/ssh to query the version if available.Affected if Firmware version is exactly 15.11.0.6
-
Check if remote web management is enabledIn the device web interface, navigate to Advanced Settings or Security settings and look for Remote Web Management, Remote Access, or WAN Access settings. Verify whether the feature is turned ON.Affected if Remote web management is enabled and the device is accessible from the WAN interface
-
Verify the device is exposed to external networkCheck your network firewall or router configuration to determine if the Tenda W20E HTTP (port 80) or HTTPS (port 443) services are accessible from the internet/WAN side.Affected if The device admin interface is reachable from external IP addresses
-
Inspect the vulnerable endpointIf remote access is enabled, send an HTTP POST request to http://[deviceIP]/goform/SetRemoteWebManage with an oversized remoteIP parameter value (e.g., very long string) to confirm the vulnerability exists.Affected if The device responds to requests on the /goform/SetRemoteWebManage endpoint with oversized remoteIP values without proper bounds checking
The device is affected only if it is a Tenda W20E running exactly firmware version 15.11.0.6 with remote web management enabled and accessible from an external network.
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 dataSince the vendor has not responded to the disclosure, apply workarounds: disable remote web management via the device administrative interface if possible, or restrict external access to the device's HTTP/HTTPS ports using network firewall rules. Consider replacing the device if no firmware update becomes available.
- 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-3874 — 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-3874 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