CVE-2024-25756
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 Stack Based Buffer Overflow vulnerability in Tenda AC9 v.3.0 with firmware version v.15.03.06.42_multi allows a remote attacker to execute arbitrary code via the formWifiBasicSet function.
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 stack-based buffer overflow exists in the formWifiBasicSet function of Tenda AC9 v3.0 firmware v.15.03.06.42_multi. The function likely fails to properly validate the length of user-supplied WiFi configuration input before copying it to a fixed-size stack buffer, allowing a remote attacker to overwrite return addresses and achieve arbitrary code execution.
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= 5.03.06.42_multiCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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.
-
Identify device model and firmware versionAccess the Tenda router web interface (usually at 192.168.0.1) and navigate to System Settings > Firmware Upgrade, or use the 'ver' command via UART/SSH if available. Alternatively, extract the firmware binary and check the version string.Affected if The firmware version is exactly 15.03.06.42_multi (or 5.03.06.42_multi as listed in the advisory).
-
Confirm the web management interface is accessibleAttempt to access the router's web interface from the network segment where management is expected (typically the LAN, but for remote exploitation from the WAN, check if remote management is enabled under System Settings > Remote Management).Affected if The web interface at formWifiBasicSet is reachable over the network (either LAN or WAN if remote management is enabled).
-
Identify if the vulnerable formWifiBasicSet function is exposedThe formWifiBasicSet function handles WiFi basic settings. Check if the WiFi configuration page (/goform/formWifiBasicSet or similar) is accessible by attempting a GET request to the router's web interface and locating the WiFi settings form.Affected if The WiFi settings form (formWifiBasicSet) is accessible and accepts user-supplied input for SSID or other WiFi parameters.
-
Check for signs of exploitationReview router logs for unusual POST requests to /goform/formWifiBasicSet with abnormally long parameter values, or monitor network traffic for such patterns. Check for unexpected new processes, modified configurations, or unknown firmware changes.Affected if Logs show POST requests to formWifiBasicSet with unusually long parameter values, or the router exhibits unexpected behavior such as new admin accounts, modified WiFi settings, or unresponsive behavior after such requests.
A user is affected if they are running Tenda AC9 v3.0 firmware version 15.03.06.42_multi and the router's web management interface (specifically the WiFi settings form) is accessible to an attacker.
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 dataIf available, apply vendor firmware update. Otherwise, disable remote management interfaces, implement network segmentation, and monitor for exploitation attempts. Consider device replacement if no patch is forthcoming.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25756 — 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-25756 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