CVE-2024-0536
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, which was classified as critical, has been found in Tenda W9 1.0.0.7(4456). Affected by this issue is the function setWrlAccessList of the component httpd. The manipulation of the argument ssidIndex leads to stack-based buffer overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-250706 is the identifier assigned to this vulnerability. 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 confidenceStack-based buffer overflow in Tenda W9 router httpd component's setWrlAccessList function allows remote attackers to overflow a stack buffer via the ssidIndex argument. The critical CVSS 9.8 score indicates trivial remote exploitation likely 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.7\(4456\)CVSS 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 device modelLog into the router web interface or check the device label to confirm it is a Tenda W9 routerAffected if Device is not a Tenda W9 model - different models are not affected by this specific CVE
-
Check firmware versionNavigate to the router admin panel (usually http://192.168.0.1), go to System Settings or Administration section, and locate the firmware version information. Alternatively, check via CLI if telnet/ssh is enabledAffected if Firmware version is 1.0.0.7(4456) - this is the exact affected version. Other versions may have different vulnerability status
-
Verify httpd service is exposedCheck if the router web management interface is accessible from the WAN/internet side by attempting to access the router's public IP on port 80/443. Review router firewall settings to determine if remote management is enabledAffected if The httpd service is reachable from untrusted networks - the vulnerability can be exploited remotely without authentication
-
Check if wireless access control is accessibleAttempt to access the setWrlAccessList function through the router's web interface by locating Wireless Access Control or Wireless MAC Filtering settings. This function handles ssidIndex parameter processingAffected if The wireless access control feature is exposed and the httpd handles the ssidIndex parameter - the buffer overflow occurs in this specific function
You are affected if you are running Tenda W9 firmware version 1.0.0.7(4456) and the router's httpd management interface is accessible (especially from WAN), as the stack-based buffer overflow in setWrlAccessList can be triggered via the ssidIndex argument without authentication.
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 no vendor patch is available, implement network segmentation to isolate the router, disable remote management interfaces if possible, and deploy WAF/IPS rules to detect exploitation attempts. Device replacement should be considered.
- Consultation6.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0536 — 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-0536 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