Ac6 FirmwareOperating system · Tenda

CVE-2023-40847

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Tenda AC6 US_AC6V1.0BR_V15.03.05.16_multi_TD01.bin is vulnerable to Buffer Overflow via the function "initIpAddrInfo." In the function, it reads in a user-provided parameter, and the variable is passed to the function without any length check.

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 · moderate confidence

Buffer overflow vulnerability in Tenda AC6 router firmware (US_AC6V1.0BR_V15.03.05.16_multi_TD01.bin) in the initIpAddrInfo function. The function accepts user input and passes it to another function without validating the input length, allowing an attacker to overflow buffers and potentially achieve remote code execution.

MitigationApply vendor firmware update when available; otherwise, restrict network access to the router's management interface via firewall rules or network segmentation to reduce attack surface.

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
Ac6 FirmwareOperating system
Affected:= 15.03.05.16

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
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 checks

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

  1. Confirm device model is Tenda AC6
    Access router web interface or check device label/marking to verify the model is Tenda AC6
    Affected if Device is not a Tenda AC6 router
  2. Check installed firmware version
    Log into the router admin panel and navigate to System Settings > Firmware Upgrade, or use telnet/ssh to access the device and run 'cat /proc/version' or check /etc/firmware_version if available
    Affected if Firmware version is 15.03.05.16
  3. Identify exposure of vulnerable interface
    Review router web interface or API endpoints for any functionality that invokes the initIpAddrInfo function - this is typically related to IP address configuration in network settings
    Affected if The initIpAddrInfo function is exposed via an accessible web CGI, API, or network service
  4. Check network accessibility of management interface
    Verify if router admin interface (typically ports 80/443) is reachable from untrusted networks by scanning external-facing IP ranges
    Affected if Router management interface is exposed to WAN or untrusted networks without firewall restrictions

The environment is affected if the Tenda AC6 router is running firmware version 15.03.05.16 and the initIpAddrInfo function is accessible through an exposed interface.

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

Apply vendor firmware update when available; otherwise, restrict network access to the router's management interface via firewall rules or network segmentation to reduce attack surface.

Fix this in Ac6 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40847 — 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-2023-40847 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