# CVE-2020-1863: Denial of service in Huawei USG6000V

> A remote unauthenticated attacker can cause a denial of service in Huawei USG6000V firewalls via an out-of-bounds read in JSON parsing.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 12 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7g8j-868p-v8q4

## What is CVE-2020-1863?

CVE-2020-1863 is a high-severity denial of service vulnerability in Huawei USG6000V, published on 12 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei USG6000V with versions V500R001C20SPC300, V500R003C00SPC100, and V500R005C00SPC100 have an out-of-bounds read vulnerability. Due to a logical flaw in a JSON parsing routine, a remote, unauthenticated attacker could exploit this vulnerability to disrupt service in the affected products.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2020-1863?

It affects 1 product.


Products: Huawei Usg6000v Firmware.

## How do I fix CVE-2020-1863?

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

## Is CVE-2020-1863 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1863 and fix it if it is affected.

What it is: CVE-2020-1863 is a high-severity denial of service vulnerability in Huawei USG6000V, published on 12 Mar 2020. 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-2020-1863 in the wild and no public exploit code.

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

## Sources

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

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