# CVE-2019-5307: Other in P30,P30 Pro

> Attackers can replay NAS messages via rogue base stations to tamper with GUTIs or obtain IMSIs on Huawei P30 devices.

- **Severity:** Medium 4.2 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **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-f9r5-w77x-85qf

## What is CVE-2019-5307?

CVE-2019-5307 is a medium-severity vulnerability in Huawei P30,P30 Pro, 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

Some Huawei 4G LTE devices, P30 versions before ELE-AL00 9.1.0.162(C01E160R1P12/C01E160R2P1) and P30 Pro versions before VOG-AL00 9.1.0.162(C01E160R1P12/C01E160R2P1), are exposed to a message replay vulnerability. For the sake of better compatibility, these devices implement a less strict check on the NAS message sequence number (SN), specifically NAS COUNT. As a result, an attacker can construct a rogue base station and replay the GUTI reallocation command message in certain conditions to tamper with GUTIs, or replay the Identity request message to obtain IMSIs. (Vulnerability ID: HWPSIRT-2019-04107)

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 2 products.


Products: Huawei P30 Firmware, Huawei P30 Pro Firmware.

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

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

## Is CVE-2019-5307 being exploited?

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

## Other vulnerabilities in Huawei P30,P30 Pro

- [CVE-2020-1800](https://insights.sbomify.com/CVE-2020-1800/): Missing authorization in HUAWEI P30 (high 7.8)
- [CVE-2020-1812](https://insights.sbomify.com/CVE-2020-1812/): Auth bypass in HUAWEI P30 (high 7.8)
- [CVE-2019-5287](https://insights.sbomify.com/CVE-2019-5287/): Integer overflow in P30 (high 7.8)
- [CVE-2019-5288](https://insights.sbomify.com/CVE-2019-5288/): Integer overflow in P30 (high 7.8)
- [CVE-2021-22331](https://insights.sbomify.com/CVE-2021-22331/): Cross-site scripting in HUAWEI P30 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5307 is a medium-severity vulnerability in Huawei P30,P30 Pro, 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-5307 in the wild and no public exploit code.

Affected product: Huawei P30,P30 Pro. 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-5307/ (Markdown: https://insights.sbomify.com/CVE-2019-5307/index.md)
```

## Sources

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

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