CVE-2022-46435
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 · uneditedAn issue in the firmware update process of TP-Link TL-WR941ND V2/V3 up to 3.13.9 and TL-WR941ND V4 up to 3.12.8 allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via uploading a crafted firmware image.
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 confidenceThe TP-Link TL-WR941ND wireless router (V2/V3 up to firmware 3.13.9 and V4 up to 3.12.8) contains a vulnerability in its firmware update mechanism. The device fails to properly validate or sanitize crafted firmware images uploaded during the update process, allowing an attacker to achieve arbitrary code execution or trigger a denial of service condition.
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<= 3.13.9<= 3.13.9<= 3.12.8CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is TL-WR941NDInspect the device label or access the router web interface (typically at 192.168.0.1) and check the device model displayed on the status or management pageAffected if Device is not a TL-WR941ND - different models are not affected by this CVE
-
Identify hardware version (V2, V3, or V4)Check the sticker on the router device itself or look for hardware version information in the web interface under Status or System > Hardware InfoAffected if Hardware version is not V2, V3, or V4 - other hardware versions may have different patch status
-
Locate firmware version in web interfaceLogin to the router web interface, navigate to Status page or System Tools > Firmware Upgrade, and note the displayed firmware version numberAffected if Unable to retrieve firmware version from the interface
-
Compare V2/V3 firmware version against affected rangeIf hardware version is V2 or V3, compare the installed firmware version (for example, 3.13.9) to the affected range: any version <= 3.13.9 is vulnerableAffected if Firmware version is V2 or V3 and is <= 3.13.9 - the device is affected by the vulnerable update mechanism
-
Compare V4 firmware version against affected rangeIf hardware version is V4, compare the installed firmware version to the affected range: any version <= 3.12.8 is vulnerableAffected if Firmware version is V4 and is <= 3.12.8 - the device is affected by the vulnerable update mechanism
The device is affected if it is a TL-WR941ND with hardware version V2 or V3 running firmware <= 3.13.9, or hardware version V4 running firmware <= 3.12.8.
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.
dbcve · scopedApply the latest patched firmware version from TP-Link if available; if the device is end-of-life and no patch exists, replace the device or implement network segmentation to restrict access to the firmware update interface.
Latest firmware version available on TP-Link support website for TL-WR941ND (V2/V3/V4) - versions higher than 3.13.9 for V2/V3 and higher than 3.12.8 for V4
- 1. Navigate to the official TP-Link support page: https://www.tp-link.com/support/
- 2. Enter "TL-WR941ND" in the search or support lookup field
- 3. Select your specific hardware version (V2, V3, or V4)
- 4. Locate the firmware download section
- 5. Download the latest available firmware version for your hardware version
- 6. Access your router's web management interface (typically http://192.168.0.1 or http://192.168.1.1)
- 7. Navigate to System Tools > Firmware Upgrade (or similar path)
- 8. Upload the downloaded firmware file and initiate the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46435 — 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-46435 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