CVE-2020-24363
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 · uneditedTP-Link TL-WA855RE V5 20200415-rel37464 devices allow an unauthenticated attacker (on the same network) to submit a TDDP_RESET POST request for a factory reset and reboot. The attacker can then obtain incorrect access control by setting a new administrative password.
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-WA855RE V5 range extender contains an authentication bypass vulnerability in its TDDP (TP-Link Diagnostic Protocol) service. An unauthenticated attacker on the same local network can send a specially crafted TDDP_RESET POST request to trigger a factory reset and reboot. Following the reset, the attacker can set a new administrative password, gaining full control of the device.
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< 200731CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device firmware versionAccess the device's web admin interface and navigate to the Status or System settings page to view the current firmware version. Alternatively, log into the device via SSH or use the TP-Link Tether mobile app to check the firmware version displayed.Affected if The installed firmware version is < 200731 (any version before July 31, 2020).
-
Verify the TDDP service is reachableFrom a machine on the same network segment as the extender, attempt to reach the TDDP service on UDP port 1040 using a network scanner or by sending a probe packet to the device's IP address on UDP port 1040.Affected if The TDDP service responds to UDP port 1040 requests, indicating it is enabled and accessible.
-
Confirm the device is on an accessible networkReview your network topology to determine if the TP-Link extender is placed on the same broadcast network segment as untrusted or guest devices. Check if the device's management interface is reachable from networks that contain untrusted hosts.Affected if The device is reachable from network segments that contain untrusted or attacker-proximal hosts without network isolation.
-
Inspect for unauthorized admin accountsLog into the device admin interface and navigate to the Administration or Access Control settings. Look for any admin accounts that were not created by you, or check if the admin password has been changed without your knowledge.Affected if New or unexpected admin accounts exist, or the administrator password has been changed from its previously known value.
A user is affected if their TP-Link TL-WA855RE V5 device runs firmware version < 200731, the TDDP service on UDP port 1040 is accessible from their network, and the device is not isolated from untrusted network segments.
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 · scoped200731
Apply vendor firmware updates when available; in the interim, isolate affected devices on dedicated network segments and restrict access to the device's management interface to prevent unauthorized local network attackers from exploiting this vulnerability.
TP-Link TL-WA855RE Firmware version 200731 or later
- Identify the current firmware version of the TP-Link TL-WA855RE device through the web management interface or mobile app
- Navigate to the TP-Link official support page for the TL-WA855RE model
- Download the latest firmware version 200731 or later from the official TP-Link support site
- Access the device's web management interface (typically at 192.168.0.1 or tplinkrepeater.net)
- Go to the Firmware Upgrade or System Tools section
- Upload and apply the downloaded firmware file
- Allow the device to complete the firmware upgrade process without interruption
- After reboot, verify the new firmware version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24363 — 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-2020-24363 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