dbcve.org
W9 FirmwareOperating system · Tenda

CVE-2024-4244

HIGH · 8.8 CVSS v3.1 Published 2024-04-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A vulnerability classified as critical was found in Tenda W9 1.0.0.7(4456). Affected by this vulnerability is the function fromDhcpSetSer of the file /goform/DhcpSetSer. The manipulation of the argument dhcpStartIp/dhcpEndIp/dhcpGw/dhcpMask/dhcpLeaseTime/dhcpDns1/dhcpDns2 leads to stack-based buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-262135. 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 confidence

Stack-based buffer overflow in Tenda W9 router's DHCP configuration function /goform/DhcpSetSer allows remote attackers to overflow stack buffers via oversized dhcpStartIp, dhcpEndIp, dhcpGw, dhcpMask, dhcpLeaseTime, dhcpDns1, or dhcpDns2 parameters. The vulnerability is exploitable remotely with public exploit code available, enabling potential remote code execution.

MitigationSince Tenda did not respond to disclosure, no vendor patch is expected. Implement compensating controls: disable remote administration via WAN, restrict admin interface access to trusted networks only, or replace the end-of-life 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
W9 FirmwareOperating system
Affected:= 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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the router admin interface or check the device label/marketing to confirm it is a Tenda W9 router
    Affected if Device is not a Tenda W9 model
  2. Check the firmware version
    Log into the router web interface, typically at 192.168.0.1, and navigate to System Settings > Firmware Upgrade or Status page to view the installed firmware version. Alternatively, check via CLI if telnet/ssh is enabled
    Affected if Firmware version is 1.0.0.7(4456)
  3. Verify the DHCP web interface is reachable
    Attempt to access the URI /goform/DhcpSetSer on the router's web interface (e.g., http://192.168.0.1/goform/DhcpSetSer). This endpoint handles DHCP configuration
    Affected if The /goform/DhcpSetSer endpoint responds (indicates the vulnerable function is present)
  4. Confirm remote administration is enabled
    Check the router's WAN settings for Remote Management/Remote Access features. Look for options like 'Remote Management', 'Web Management Port', or 'Allow WAN Access' typically under Advanced > Remote Management or System Tools > Administration
    Affected if Remote management via WAN is enabled, allowing unauthenticated or low-privilege attackers to reach the vulnerable DHCP function from the internet

The environment is affected if it is a Tenda W9 router running firmware version 1.0.0.7(4456) with the /goform/DhcpSetSer endpoint accessible, especially if remote WAN administration is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since Tenda did not respond to disclosure, no vendor patch is expected. Implement compensating controls: disable remote administration via WAN, restrict admin interface access to trusted networks only, or replace the end-of-life device.

Fix this in W9 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4244 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4244 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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