dbcve.org
Re3000 FirmwareOperating system · Tp Link

CVE-2022-41783

MEDIUM · 5.5 CVSS v3.1 Published 2022-12-07
Fix available
A fix is available. Upgrade to 221009 or later.
See remediation →
57/100
Remediation priority · Elevated
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
tdpServer of TP-Link RE300 V1 improperly processes its input, which may allow an attacker to cause a denial-of-service (DoS) condition of the product's OneMesh function.

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

The tdpServer (likely TP-Link Discovery Protocol server) in the TP-Link RE300 V1 range extender fails to properly validate or process input data. This improper input handling can be exploited by an attacker to crash the tdpServer process, resulting in a denial-of-service condition that disables the device's OneMesh functionality.

MitigationContact TP-Link for available firmware updates. In the interim, isolate the device on a restricted network segment to limit attack surface, and monitor for unusual OneMesh availability issues.

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
Re3000 FirmwareOperating system
Affected:< 221009

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Confirm device model
    Access the TP-Link RE300 web interface or check the device label to verify the exact model number is RE300 V1
    Affected if Device is a TP-Link RE300 V1 range extender
  2. Check firmware version
    Log into the RE300 web UI and navigate to Status or System settings to view the installed firmware version. Compare against 221009
    Affected if Firmware version is less than 221009 (e.g., 220928, older)
  3. Verify tdpServer availability
    Access the device via SSH or telnet if enabled and run: ps | grep tdpServer or check if the tdpServer process is running. Alternatively, check the web UI status page for OneMesh server status
    Affected if tdpServer process is not running or OneMesh server shows unavailable
  4. Test OneMesh functionality
    Attempt to add or detect OneMesh nodes through the TP-Link Tether app or web interface. Check if OneMesh feature responds or fails to initialize
    Affected if OneMesh functionality fails to initialize or reports as disabled
  5. Check for crash indicators
    Review system logs via the web UI (if available) or check for repeated device reboots or connectivity drops that coincide with discovery protocol activity
    Affected if Frequent crashes or reboots occur and OneMesh becomes unavailable after network discovery traffic

You are affected if you have a TP-Link RE300 V1 running firmware version below 221009 and OneMesh functionality is unavailable or the tdpServer process is not running.

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

Contact TP-Link for available firmware updates. In the interim, isolate the device on a restricted network segment to limit attack surface, and monitor for unusual OneMesh availability issues.

Recommended fix Moderate confidence

Firmware version 221009 or later

  1. 1. Visit the official TP-Link support website at https://www.tp-link.com/
  2. 2. Navigate to the RE300 V1 product page and go to Support/Firmware section
  3. 3. Download the firmware version 221009 or later
  4. 4. Access the TP-Link RE300 web management interface
  5. 5. Go to System Tools > Firmware Upgrade (or similar section)
  6. 6. Upload the downloaded firmware file and wait for the upgrade to complete
  7. 7. Verify the firmware version has been updated successfully

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

Fix this in Re3000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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