dbcve.org
Ac1750 FirmwareOperating system · Tp Link

CVE-2022-24353

HIGH · 8.8 CVSS v3.1 Published 2023-03-28
Fix available
A fix is available. Upgrade to 211210 or later.
See remediation →
93/100
Remediation priority · Urgent
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
This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of TP-Link AC1750 1.1.4 Build 20211022 rel.59103(5553) routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the NetUSB.ko module. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the root user. Was ZDI-CAN-15769.

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

Buffer over-read vulnerability in the NetUSB.ko module of TP-Link AC1750 routers (firmware 1.1.4 Build 20211022). Unauthenticated network-adjacent attackers can exploit the lack of proper validation of user-supplied data to read past the end of an allocated buffer and execute arbitrary code in the context of the root user.

MitigationApply vendor firmware update when available; until then, restrict network adjacency to the router's management interface and disable unnecessary services 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
Ac1750 FirmwareOperating system
Affected:< 211210

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

CVSS:3.1/AV:A/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 router model is TP-Link AC1750
    Access router admin interface or check device label/model number
    Affected if Router is not a TP-Link AC1750 model
  2. Check installed firmware version
    Navigate to router admin panel System or Firmware Upgrade section to view current firmware build number; compare against 211210
    Affected if Firmware version/build number is less than 211210
  3. Verify NetUSB.ko module presence
    Check router firmware filesystem or module directory for NetUSB.ko file; on Linux-based routers, inspect /lib/modules/ or use lsmod to list loaded kernel modules
    Affected if NetUSB.ko module exists and is loaded/enabled on the device

Device is affected if it is a TP-Link AC1750 router running firmware version below 211210 with the NetUSB.ko module present and enabled.

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 211210 or later
Fixed in 211210
Interim mitigation

Apply vendor firmware update when available; until then, restrict network adjacency to the router's management interface and disable unnecessary services to reduce attack surface.

Recommended fix High confidence

TP-Link AC1750 Firmware version 211210 or later

  1. 1. Log into the TP-Link AC1750 router administration interface (typically at 192.168.0.1 or 192.168.1.1)
  2. 2. Navigate to the Firmware Upgrade or System Tools section
  3. 3. Identify the current firmware version under Status or System Info
  4. 4. Download the firmware version 211210 or later from TP-Link's official support website (support.tp-link.com) for the specific AC1750 model
  5. 5. In the router admin interface, locate the Firmware Upgrade option
  6. 6. Click Browse/Select and choose the downloaded firmware file
  7. 7. Click Upgrade and wait for the update to complete (do not power off the router during this process)
  8. 8. After reboot, verify the new firmware version is 211210 or later under Status
Caveat Firmware updates may temporarily disrupt network connectivity; ensure stable power during upgrade

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

Fix this in Ac1750 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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