# CVE-2019-16893: Missing authorization in n/a

> An unauthenticated attacker can reboot the TP-Link managed switch by accessing a specific CGI endpoint, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4hhj-cvff-6mw4

## What is CVE-2019-16893?

CVE-2019-16893 is a high-severity missing authorization vulnerability in n/a, published on 3 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Web Management of TP-Link TP-SG105E V4 1.0.0 Build 20181120 devices allows an unauthenticated attacker to reboot the device via a reboot.cgi request.

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

## Which versions are affected by CVE-2019-16893?

It affects 1 product.


Products: Tp-Link Tp-Sg105e Firmware.

## How do I fix CVE-2019-16893?

No fix has been published for CVE-2019-16893 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-16893 being exploited?

There is no known exploitation of CVE-2019-16893 in the wild and no public exploit code.

Public exploit code:

- TP-Link TP-SG105E 1.0.0 - Unauthenticated Remote Reboot (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16893 and fix it if it is affected.

What it is: CVE-2019-16893 is a high-severity missing authorization vulnerability in n/a, published on 3 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-16893 in the wild and no public exploit code.

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-2019-16893/ (Markdown: https://insights.sbomify.com/CVE-2019-16893/index.md)
```

## Sources

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

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