CVE-2022-41480
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 · uneditedTenda AC1200 US_AC6V2.0RTL_V15.03.06.51_multi_TDE01 was discovered to contain a buffer overflow in the 0x475dc 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 confidenceA buffer overflow vulnerability exists in the 0x475dc function of Tenda AC1200 router firmware version US_AC6V2.0RTL_V15.03.06.51_multi_TDE01. Attackers can send a crafted request to trigger the overflow, causing a Denial of Service. The vulnerability is exploitable remotely without authentication.
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= 15.03.06.51CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Tenda AC1200 model variantLocate the model number on the router label or check the web interface (usually under System Info or Status page). Confirm it is the AC6 v2.0 model.Affected if Model is not Tenda AC6 v2.0 (the only affected model)
-
Check installed firmware versionAccess the router web interface, navigate to System Settings or Administration > Firmware Upgrade. The firmware version is displayed on the main status page or system info section. Alternatively, if you have extracted the firmware binary, check the version string within the image.Affected if Firmware version is exactly 15.03.06.51 (US_AC6V2.0RTL_V15.03.06.51_multi_TDE01)
-
Verify web management interface is enabledCheck the router configuration under System Settings or Administration > Remote Management. Confirm that the HTTP/HTTPS management interface is accessible from the WAN (Internet) side or is enabled for remote access.Affected if Remote web management is enabled, exposing the vulnerable function to network requests
-
Confirm the 0x475dc function is reachableThe vulnerable function is invoked via specific HTTP requests to the web server. If the device is reachable on the network (LAN or WAN IP on port 80/443), the function can be triggered. Use a port scanner to confirm ports 80 or 443 are open and responding.Affected if The router web interface is accessible from a network (indicating the attack surface exists)
You are affected only if you have a Tenda AC6 v2.0 router running firmware version 15.03.06.51 with the web interface accessible on your network.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor-provided firmware patch when available. Until then, restrict network access to the device's management interface using firewall rules or ACLs to limit exposure to untrusted networks.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41480 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41480 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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