CVE-2024-4165
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, was found in Tenda G3 15.11.0.17(9502). Affected is the function modifyDhcpRule of the file /goform/modifyDhcpRule. The manipulation of the argument bindDhcpIndex leads to stack-based buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-261984. 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 G3 router firmware 15.11.0.17 allows remote code execution via the `bindDhcpIndex` parameter in the /goform/modifyDhcpRule web interface function. The vulnerability is remotely exploitable without authentication and a public exploit exists, enabling full compromise of 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.17\(9502\)_cnCVSS 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 modelAccess the router web interface or check the device label to confirm it is a Tenda G3 router. Alternatively, inspect the HTTP Server header or check the admin login page for Tenda G3 branding.Affected if The device is not a Tenda G3 router.
-
Check firmware versionLog into the router web interface and navigate to the System Status or Firmware Version page. Alternatively, use the Tenda admin panel or check the firmware file if you have access to the firmware image.Affected if The firmware version is exactly 15.11.0.17 (9502)_cn.
-
Verify web interface is accessibleAttempt to access the router web interface by navigating to the router IP address (commonly 192.168.0.1 or 192.168.1.1) in a web browser. Confirm the /goform/modifyDhcpRule endpoint responds to HTTP requests.Affected if The web interface is not exposed or the /goform/modifyDhcpRule endpoint does not exist.
-
Check network exposure of the web interfaceDetermine if the router web interface is accessible from the public internet or an untrusted network segment. Use an external IP scan or review firewall rules to see if ports 80 or 443 are open to untrusted interfaces.Affected if The router web interface is exposed to the internet or untrusted networks without firewall protection.
-
Inspect the vulnerable parameter availabilitySend an HTTP POST request to /goform/modifyDhcpRule with the bindDhcpIndex parameter. This requires the DHCP configuration feature to be present in the web interface.Affected if The modifyDhcpRule function with bindDhcpIndex parameter is not present or the DHCP configuration feature is disabled.
You are affected if you have a Tenda G3 router running firmware version 15.11.0.17 (9502)_cn with the web interface accessible and the modifyDhcpRule function available.
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 the affected device on a restricted network segment and consider replacement, as Tenda has not responded to the disclosure and no vendor patch is available. A WAF or intrusion prevention system may filter exploitation attempts targeting the web interface.
- Consultation4.0 h
- Implementation2.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4165 — 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-4165 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