# CVE-2023-22303: Auth bypass in TP-Link SG105PE

> An attacker can bypass authentication to impersonate an administrator, allowing them to read information and modify settings on the TP-Link SG105PE switch.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 17 Jan 2023
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-w8m5-v6rc-xwx3

## What is CVE-2023-22303?

CVE-2023-22303 is a critical authentication bypass vulnerability in TP-Link SG105PE, published on 17 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TP-Link SG105PE firmware prior to 'TL-SG105PE(UN) 1.0_1.0.0 Build 20221208' contains an authentication bypass vulnerability. Under the certain conditions, an attacker may impersonate an administrator of the product. As a result, information may be obtained and/or the product's settings may be altered with the privilege of the administrator.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-22303?

It affects 1 product.


Products: Tp-Link Tl-Sg105pe Firmware.

## How do I fix CVE-2023-22303?

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

## Is CVE-2023-22303 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22303 and fix it if it is affected.

What it is: CVE-2023-22303 is a critical authentication bypass vulnerability in TP-Link SG105PE, published on 17 Jan 2023. 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-2023-22303 in the wild and no public exploit code.

Affected product: TP-Link SG105PE. 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-2023-22303/ (Markdown: https://insights.sbomify.com/CVE-2023-22303/index.md)
```

## Sources

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

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