CVE-2024-2856
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 AC10 16.03.10.13/16.03.10.20. Affected by this issue is the function fromSetSysTime of the file /goform/SetSysTimeCfg. The manipulation of the argument timeZone leads to stack-based buffer overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-257780. 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 AC10 router's web interface (fromSetSysTime function in /goform/SetSysTimeCfg) allows remote unauthenticated attackers to overflow a stack buffer via the unvalidated timeZone parameter, potentially achieving remote 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= 16.03.10.13= 16.03.10.20CVSS 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's admin web interface (usually at 192.168.0.1 or similar) and look for the model name in the status or system information page. Alternatively, check the device label or packaging.Affected if The device is not a Tenda AC10 router (the vulnerability only affects this specific model).
-
Check the firmware versionIn the router's web admin interface, navigate to System Settings > Firmware Update or System Status to find the firmware version. Alternatively, use curl to request the main page and look for version strings in the HTML source.Affected if The firmware version is 16.03.10.13 or 16.03.10.20 exactly.
-
Verify web interface accessibilityAttempt to access the router's web interface from an external network (or use nmap from a remote host to check if ports 80/443 are open): nmap -p 80,443 <router-public-IP>. Try accessing http://<router-IP>/goform/SetSysTimeCfg directly.Affected if The web interface is accessible from untrusted networks (the internet or non-local subnets).
-
Check for the vulnerable endpointSend a request to the vulnerable endpoint using curl: curl -X POST http://<router-IP>/goform/SetSysTimeCfg -d "timeZone=test". A response (even an error) indicates the endpoint exists and may be reachable.Affected if The /goform/SetSysTimeCfg endpoint responds without requiring authentication.
You are affected if you have a Tenda AC10 router running firmware version 16.03.10.13 or 16.03.10.20 with its web interface exposed to untrusted networks.
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 dataIsolate affected devices from untrusted networks; block external access to the router's web interface (port 80/443). Monitor for Indicators of Compromise since no vendor patch exists.
- Consultation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2856 — 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-2856 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