# CVE-2019-19411: Weak cryptography in USG9500

> Improper IV processing in USG9500 encryption allows attackers to diminish confidentiality and potentially read sensitive data.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v34h-3hv8-mwm9

## What is CVE-2019-19411?

CVE-2019-19411 is a low-severity vulnerability in Huawei Usg9500 Firmware, published on 21 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

USG9500 with versions of V500R001C30SPC100, V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00SPC100, V500R005C00SPC200 have an information leakage vulnerability. Due to improper processing of the initialization vector used in a specific encryption algorithm, an attacker who gains access to this cryptographic primitive may exploit this vulnerability to cause the value of the confidentiality associated with its use to be diminished.

Weakness: CWE-665 (Improper Initialization)

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

It affects 1 product.


Products: Huawei Usg9500 Firmware.

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

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

## Is CVE-2019-19411 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-19411 exists.

Public exploit code:

- Huawei Firewall - Local File Inclusion (nuclei): http/cves/2019/CVE-2019-19411.yaml

## Other vulnerabilities in Huawei Usg9500 Firmware

- [CVE-2020-1871](https://insights.sbomify.com/CVE-2020-1871/): Information disclosure in USG9500 (high 8.2)
- [CVE-2021-22309](https://insights.sbomify.com/CVE-2021-22309/): Weak cryptography in USG9500,USG9520,USG9560,USG9580 (high 7.5)
- [CVE-2019-5273](https://insights.sbomify.com/CVE-2019-5273/): Memory corruption in USG9500 (high 7.5)
- [CVE-2019-5274](https://insights.sbomify.com/CVE-2019-5274/): Denial of service in USG9500 (high 7.5)
- [CVE-2019-5275](https://insights.sbomify.com/CVE-2019-5275/): Memory corruption in USG9500 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19411 is a low-severity vulnerability in Huawei Usg9500 Firmware, published on 21 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-19411 exists.

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

## Sources

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

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