# CVE-2019-5298: Auth bypass in AP4050DN-E

> An attacker with physical access can bypass serial port authentication on Huawei APs to execute arbitrary commands and gain elevated privileges.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pv76-f73p-j7vq

## What is CVE-2019-5298?

CVE-2019-5298 is a medium-severity authentication bypass vulnerability in Huawei AP4050DN-E, published on 4 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is an improper authentication vulnerability in some Huawei AP products before version V200R009C00SPC800. Due to the improper implementation of authentication for the serial port, an attacker could exploit this vulnerability by connecting to the affected products and running a series of commands.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Huawei Ap4050dn-E Firmware.

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

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

## Is CVE-2019-5298 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5298 is a medium-severity authentication bypass vulnerability in Huawei AP4050DN-E, published on 4 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5298 in the wild and no public exploit code.

Affected product: Huawei AP4050DN-E. 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-5298/ (Markdown: https://insights.sbomify.com/CVE-2019-5298/index.md)
```

## Sources

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

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