# CVE-2019-5291: Other in AR120-S;AR1200;AR1200-S;AR150;AR150-S;AR160;AR200;AR200-S;AR2200;AR2200-S;AR3200;AR3600;CloudEngine 12800;NetEngine16EX;S6700;SRG1300;SRG2300;SRG3300

> Remote attackers can cause denial of service on Huawei network devices by intercepting and modifying specific data packets due to insufficient verification.

- **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-x6v5-8qcc-4q56

## What is CVE-2019-5291?

CVE-2019-5291 is a medium-severity vulnerability in Huawei Ar3200 Firmware, published on 13 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Some Huawei products have an insufficient verification of data authenticity vulnerability. A remote, unauthenticated attacker has to intercept specific packets between two devices, modify the packets, and send the modified packets to the peer device. Due to insufficient verification of some fields in the packets, an attacker may exploit the vulnerability to cause the target device to be abnormal.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 18 products.


Products: Huawei Ar120-S Firmware, Huawei Ar1200-S Firmware, Huawei Ar1200 Firmware, Huawei Ar150-S Firmware, Huawei Ar150 Firmware, Huawei Ar160 Firmware, Huawei Ar200-S Firmware, Huawei Ar200 Firmware, Huawei Ar2200-S Firmware, Huawei Ar2200 Firmware, Huawei Ar3200 Firmware, Huawei Ar3600 Firmware, Huawei Cloudengine 12800 Firmware, Huawei Netengine16ex Firmware, Huawei S6700 Firmware, Huawei Srg1300 Firmware, Huawei Srg2300 Firmware, Huawei Srg3300 Firmware.

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

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

## Is CVE-2019-5291 being exploited?

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

## Other vulnerabilities in Huawei Ar3200 Firmware

- [CVE-2017-17301](https://insights.sbomify.com/CVE-2017-17301/): Weak cryptography in AR120-S,AR1200,AR1200-S,AR150,AR160,AR200,AR200-S,AR2200,AR2200-S,AR3200,AR3600,AR510,CloudEngine 12800,CloudEngine 5800,CloudEngine 6800,CloudEngine 7800,DP300,SMC2.0,SRG1300,SRG2300,SRG3300,TE30,TE60,VP9660,ViewPoint 8660,eSpace IAD,eSpace U1981,eSpace USM (critical 9.8)
- [CVE-2019-19415](https://insights.sbomify.com/CVE-2019-19415/): Denial of service in AR120-S (high 7.5)
- [CVE-2019-19416](https://insights.sbomify.com/CVE-2019-19416/): Denial of service in AR120-S (high 7.5)
- [CVE-2019-19417](https://insights.sbomify.com/CVE-2019-19417/): Denial of service in AR120-S (high 7.5)
- [CVE-2019-5304](https://insights.sbomify.com/CVE-2019-5304/): Denial of service in AR120-S;AR1200;AR1200-S;AR150;AR150-S;AR160;AR200;AR200-S;AR2200;AR2200-S;AR3200;AR3600;IPS Module;NGFW Module;NIP6300;NIP6600;NetEngine16EX;S5700;S6700;SRG1300;SRG2300;SRG3300;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600 (high 7.5)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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