# CVE-2019-5253: Auth bypass in E5572-855

> An improper authentication flaw allows attackers to trigger a device reboot via man-in-the-middle attacks on Huawei E5572-855 hotspots.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 13 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q3vg-9c63-45pw

## What is CVE-2019-5253?

CVE-2019-5253 is a medium-severity authentication bypass vulnerability in E5572-855, published on 13 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

E5572-855 with versions earlier than 8.0.1.3(H335SP1C233) has an improper authentication vulnerability. The device does not perform a sufficient authentication when doing certain operations, successful exploit could allow an attacker to cause the device to reboot after launch a man in the middle attack.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Huawei E5572-855 Firmware.

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

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

## Is CVE-2019-5253 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5253 is a medium-severity authentication bypass vulnerability in E5572-855, published on 13 Dec 2019. 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-5253 in the wild and no public exploit code.

Affected product: E5572-855. 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-5253/ (Markdown: https://insights.sbomify.com/CVE-2019-5253/index.md)
```

## Sources

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

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