CVE-2024-4239
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 AX1806 1.0.0.1 and classified as critical. Affected by this issue is the function formSetRebootTimer of the file /goform/SetRebootTimer. The manipulation of the argument rebootTime 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-262130 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 confidenceA stack-based buffer overflow vulnerability exists in the formSetRebootTimer function of Tenda AX1806 routers (firmware 1.0.0.1). The function processes the rebootTime argument without proper bounds checking, allowing an attacker to overflow a stack-based buffer by providing an overly long value, 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= 1.0.0.1CVSS 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.
-
Identify the router modelLocate the device label or check the web management interface for the exact model number (Tenda AX1806).Affected if The device is NOT a Tenda AX1806 router.
-
Check the firmware versionAccess the router's web management interface (typically at 192.168.0.1) and navigate to System Settings > Firmware Upgrade, or use the telnet/SSH interface and run 'cat /etc/version' or 'ver' to retrieve the firmware version.Affected if The firmware version is 1.0.0.1.
-
Verify the web management interface is activeAttempt to access the router's HTTP/HTTPS web interface on the local network.Affected if The web interface is accessible and responds to requests.
-
Confirm the formSetRebootTimer function existsInspect the firmware binary (if accessible via telnet/SSH) for the string 'formSetRebootTimer' using 'grep -r formSetRebootTimer /' or examine the httpd binary.Affected if The function handler is present in the firmware.
-
Check network exposure of the management interfaceDetermine if the router's web interface is exposed to external networks (WAN) by reviewing port forwarding rules or firewall settings, or by testing remote IP access to ports 80/443.Affected if The management interface is reachable from untrusted networks (WAN-side).
The device is affected if it is a Tenda AX1806 router running firmware version 1.0.0.1 with the web management interface accessible, as the vulnerable formSetRebootTimer function processes the rebootTime argument without bounds checking.
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 and no patch is available, implement network-level controls such as restricting access to the router's web management interface to trusted internal IPs only, or consider replacing the device with a model that receives security updates.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4239 — 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-4239 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