Ac6v2.0 FirmwareOperating system · Tenda

CVE-2022-41482

HIGH · 7.5 CVSS v3.1 Published 2022-10-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 AC1200 US_AC6V2.0RTL_V15.03.06.51_multi_TDE01 was discovered to contain a buffer overflow in the 0x47c5dc function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted request.

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

A buffer overflow vulnerability exists in the Tenda AC1200 router firmware (US_AC6V2.0RTL_V15.03.06.51) in function 0x47c5dc. The vulnerability allows remote attackers to send a crafted HTTP request that triggers the buffer overflow, resulting in denial of service. The high CVSS score (7.5) reflects the ease of exploitation and service impact.

MitigationApply any available firmware update from Tenda. If no update exists, disable remote web management interfaces, restrict administrative access to trusted IPs only, and consider network segmentation to limit exposure.

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
Ac6v2.0 FirmwareOperating system
Affected:= 15.03.06.51

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 router firmware version
    Log into the Tenda AC1200 router web administration panel and navigate to System Settings > Firmware Upgrade, or check the version label on the router device itself
    Affected if The firmware version is exactly 15.03.06.51 (US_AC6V2.0RTL_V15.03.06.51)
  2. Check remote web management status
    In the router web UI, go to Advanced Settings > Remote Management, or examine the firewall/NAT rules that may forward HTTP (port 80) or HTTPS (port 443) traffic to the router from WAN
    Affected if Remote web management is enabled and the router admin interface is accessible from the WAN/internet
  3. Verify the vulnerable HTTP endpoint exists
    Send a crafted HTTP request to the router's public IP on port 80. The vulnerability exists in function at offset 0x47c5dc. If the device responds to unauthenticated HTTP requests on WAN, the attack surface is present
    Affected if The router responds to HTTP requests from the WAN interface without requiring VPN or LAN-side access

A user is affected if their Tenda AC1200 runs firmware version 15.03.06.51 AND has remote web management exposed to the internet, allowing unauthenticated attackers to send the malicious HTTP request that triggers the buffer overflow in function 0x47c5dc.

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 any available firmware update from Tenda. If no update exists, disable remote web management interfaces, restrict administrative access to trusted IPs only, and consider network segmentation to limit exposure.

Fix this in Ac6v2.0 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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