Ax1803 FirmwareOperating system · Tenda

CVE-2024-4236

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, which was classified as critical, has been found in Tenda AX1803 1.0.0.1. This issue affects the function formSetSysToolDDNS of the file /goform/SetDDNSCfg. The manipulation of the argument serverName/ddnsUser/ddnsPwd/ddnsDomain leads to stack-based buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-262127. 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 AX1803 router firmware 1.0.0.1 allows remote attackers to overflow buffers via DDNS configuration parameters (serverName, ddnsUser, ddnsPwd, ddnsDomain) in the /goform/SetDDNSCfg formSetSysToolDDNS function. The high CVSS score reflects remote exploitability with potential for complete device compromise.

MitigationIf vendor firmware update unavailable, disable DDNS functionality, restrict access to the router's web management interface via ACLs or VPN, and consider network segmentation; end-of-life devices should be replaced.

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
Ax1803 FirmwareOperating system
Affected:= 1.0.0.1

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 router model
    Access router web interface or check device label to confirm model is Tenda AX1803
    Affected if Device is not a Tenda AX1803 router - this vulnerability only affects that specific model
  2. Check firmware version
    Log into router web interface, navigate to System Settings or Firmware Upgrade page to view installed firmware version; or use telnet/SSH and run 'cat /proc/version' or 'ver' command
    Affected if Firmware version is exactly 1.0.0.1 - only this version is listed as affected
  3. Verify DDNS is configured
    Log into router web interface, go to Advanced Settings or System Tools > DDNS section; check if any DDNS provider (such as DynDNS, No-IP, or Tenda's own DDNS) is enabled and configured with a server name, username, password, or domain
    Affected if DDNS is enabled and any of these fields are populated: serverName, ddnsUser, ddnsPwd, or ddnsDomain - the overflow occurs when processing these parameters
  4. Inspect DDNS form submission
    If DDNS is enabled, examine the /goform/SetDDNSCfg HTTP POST request (using browser dev tools or a proxy) and check if the submitted parameters contain unusually long strings that could indicate exploitation attempts
    Affected if DDNS parameters contain data exceeding typical length limits (e.g., serverName or ddnsDomain with more than 256 characters) - this may indicate active exploitation

User is affected if they have a Tenda AX1803 router running firmware version 1.0.0.1 with DDNS functionality enabled and configured.

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

If vendor firmware update unavailable, disable DDNS functionality, restrict access to the router's web management interface via ACLs or VPN, and consider network segmentation; end-of-life devices should be replaced.

Fix this in Ax1803 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing5.0 h
  • Review / QA3.0 h
22.0 hours of engineering $3,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4236 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4236 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