# CVE-2020-24363: TP-link TL-WA855RE Missing Authentication for Critical Function

> An unauthenticated attacker on the same network can trigger a factory reset and set a new admin password, gaining full control of the device.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 2 Sep 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-339j-xv49-q5p7

## What is CVE-2020-24363?

CVE-2020-24363 is a high-severity missing authorization vulnerability in n/a, published on 31 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TP-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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2020-24363?

It affects 1 product.


Products: Tp-Link Tl-Wa855re Firmware.

## How do I fix CVE-2020-24363?

No fix has been published for CVE-2020-24363 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 23 Sep 2025.

## Is CVE-2020-24363 being exploited?

Yes. Attackers have exploited CVE-2020-24363 in the wild since at least 2 Sep 2025.

Public exploit code:

- TP-Link TL-WA855RE V5_200415 - Device Reset Auth Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-10916](https://insights.sbomify.com/CVE-2020-10916/): Auth bypass in TL-WA855RE (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-24363 and fix it if it is affected.

What it is: CVE-2020-24363 is a high-severity missing authorization vulnerability in n/a, published on 31 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-24363 in the wild since at least 2 Sep 2025.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-24363/ (Markdown: https://insights.sbomify.com/CVE-2020-24363/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-24363
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-24363
- OSV: https://osv.dev/vulnerability/CVE-2020-24363

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-24363/
Summaries are generated and may contain mistakes; the official description above is the record.