# CVE-2019-5293: Denial of service in AR120-S, AR1200, AR1200-S, AR150, AR150-S, AR160, AR200, AR200-S, AR2200, AR2200-S, AR3200, AR3600, NetEngine16EX, SRG1300, SRG2300, SRG3300

> Remote attackers with operation privileges can cause service abnormalities in Huawei routers by sending specific messages, leading to denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xpg2-54xp-8xmf

## What is CVE-2019-5293?

CVE-2019-5293 is a medium-severity denial of service vulnerability in Huawei Ar3200 Firmware, published on 13 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Some Huawei products have a memory leak vulnerability when handling some messages. A remote attacker with operation privilege could exploit the vulnerability by sending specific messages continuously. Successful exploit may cause some service to be abnormal.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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

It affects 16 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 Netengine16ex Firmware, Huawei Srg1300 Firmware, Huawei Srg2300 Firmware, Huawei Srg3300 Firmware.

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

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

## Is CVE-2019-5293 being exploited?

There is no known exploitation of CVE-2019-5293 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-5293 and fix it if it is affected.

What it is: CVE-2019-5293 is a medium-severity denial of service vulnerability in Huawei Ar3200 Firmware, published on 13 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5293 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-5293/ (Markdown: https://insights.sbomify.com/CVE-2019-5293/index.md)
```

## Sources

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

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