dbcve.org
Ax1806 FirmwareOperating system · Tenda

CVE-2024-4238

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 has been found in Tenda AX1806 1.0.0.1 and classified as critical. Affected by this vulnerability is the function formSetDeviceName of the file /goform/SetOnlineDevName. The manipulation of the argument devName 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 identifier VDB-262129 was 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 confidence

A stack-based buffer overflow vulnerability in Tenda AX1806 firmware 1.0.0.1 allows remote attackers to execute arbitrary code via the devName parameter in the /goform/SetOnlineDevName endpoint. The formSetDeviceName function fails to properly validate input length before copying to a fixed-size stack buffer.

MitigationSince no vendor patch is available, restrict exposure of the router's web management interface to trusted networks only, disable remote management features, and consider network segmentation. Monitor for indicators of compromise.

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
Ax1806 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 device model and firmware version
    Access the router's web interface or check via telnet/SSH and look for the firmware version in system information or status pages. Alternatively, check the kernel log or /proc/version if telnet is available.
    Affected if The device is a Tenda AX1806 running firmware version 1.0.0.1
  2. Verify the web management interface is reachable
    Attempt to access the router's HTTP/HTTPS web interface from a browser by entering the router's IP address (commonly 192.168.0.1 or 192.168.1.1).
    Affected if The web interface is accessible, indicating the HTTP service is running
  3. Confirm the vulnerable endpoint exists
    Send a crafted HTTP POST request to /goform/SetOnlineDevName with a devName parameter. For example: curl -X POST http://<router_ip>/goform/SetOnlineDevName -d 'devName=test'. Check if the endpoint responds.
    Affected if The /goform/SetOnlineDevName endpoint responds to requests, indicating the vulnerable function is present
  4. Check for signs of device compromise
    Review router logs for unusual entries, check for unexpected new admin accounts, look for unknown processes or DNS changes. Access /var/log or the router's logging interface if available.
    Affected if Logs show unauthorized changes, unexpected processes, or indicators of remote code execution
  5. Verify network exposure of management interface
    Check if the router's web interface is accessible from outside the local network. Scan external IP ports 80/443 or check port forwarding/NAT rules on the upstream ISP gateway.
    Affected if The router's HTTP service is exposed to the internet or untrusted networks

A user is affected if they are running Tenda AX1806 firmware version 1.0.0.1 and the web management interface (containing the vulnerable /goform/SetOnlineDevName endpoint) is accessible.

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 no vendor patch is available, restrict exposure of the router's web management interface to trusted networks only, disable remote management features, and consider network segmentation. Monitor for indicators of compromise.

Fix this in Ax1806 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-4238 — 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-4238 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