dbcve.org
Tl Wr940n FirmwareOperating system · Tp Link

CVE-2022-0650

HIGH · 8.0 CVSS v3.1 Published 2023-03-28
Fix available
A fix is available. Upgrade to 211111 or later.
See remediation →
82/100
Remediation priority · High
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
This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of TP-Link TL-WR940N 3.20.1 Build 200316 Rel.34392n (5553) routers. Authentication is required to exploit this vulnerability. The specific flaw exists within the httpd service, which listens on TCP port 80 by default. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-13993.

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

Stack-based buffer overflow in the httpd service of TP-Link TL-WR940N routers (firmware 3.20.1). The vulnerability stems from insufficient length validation of user-supplied data before copying into a fixed-size stack buffer, allowing authenticated attackers to achieve arbitrary code execution with root privileges.

MitigationApply vendor firmware update when available; until then, restrict network access to the router's administrative interface and isolate the device from untrusted networks 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
Tl Wr940n FirmwareOperating system
Affected:< 211111

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 router model and firmware version
    Access the router's web interface or check the admin panel for the firmware version under System or Administration settings
    Affected if The device is a TP-Link TL-WR940N and the firmware version is 3.20.1 or any version less than 211111
  2. Confirm httpd service is active
    Check router status page or network services list to verify the httpd web service is running
    Affected if The httpd service is running and accessible on the router
  3. Determine if remote httpd access is enabled
    Inspect the router's administration or access control settings to see if remote web management is permitted
    Affected if Remote administrative access to the httpd service is enabled, allowing authenticated users to send requests to the vulnerable service

You are affected if you have a TP-Link TL-WR940N router running firmware version 3.20.1 or any version below 211111, with the httpd service accessible for authenticated users.

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.

dbcve · scoped
Upgrade available Upgrade to 211111 or later
Fixed in 211111
Interim mitigation

Apply vendor firmware update when available; until then, restrict network access to the router's administrative interface and isolate the device from untrusted networks to reduce attack surface.

Recommended fix Moderate confidence

TP-Link TL-WR940N firmware version 211111 or later

  1. 1. Connect a computer to the TP-Link TL-WR940N router via Ethernet or WiFi
  2. 2. Open a web browser and navigate to the router's web interface (typically http://192.168.0.1 or http://192.168.1.1)
  3. 3. Log in with the router's administrator credentials
  4. 4. Navigate to the System Tools or Administration section
  5. 5. Locate the Firmware Upgrade or Router Upgrade option
  6. 6. Download the latest firmware version 211111 or later from the official TP-Link support website (www.tp-link.com)
  7. 7. Upload the firmware file through the web interface and wait for the upgrade to complete
  8. 8. After the router restarts, verify the firmware version has been updated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tl Wr940n Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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