# CVE-2020-9099: Auth bypass in IPS Module; NGFW Module; NIP6300; NIP6600; NIP6800; Secospace USG6300; Secospace USG6500; Secospace USG6600; USG9500

> Attackers can bypass authentication to obtain certain permissions on Huawei firewall and IPS devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 8 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pch4-qpxr-f8xh

## What is CVE-2020-9099?

CVE-2020-9099 is a critical authentication bypass vulnerability in Huawei Ips Module Firmware, published on 8 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei products IPS Module; NGFW Module; NIP6300; NIP6600; NIP6800; Secospace USG6300; Secospace USG6500; Secospace USG6600; USG9500 with versions of V500R001C00; V500R001C20; V500R001C30; V500R001C50; V500R001C60; V500R001C80; V500R005C00; V500R005C10; V500R005C20; V500R002C00; V500R002C10; V500R002C20; V500R002C30 have an improper authentication vulnerability. Attackers need to perform some operations to exploit the vulnerability. Successful exploit may obtain certain permissions on the device.

Weakness: CWE-287 (Improper Authentication)

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

It affects 9 products.


Products: Huawei Ips Module Firmware, Huawei Ngfw Module Firmware, Huawei Nip6300 Firmware, Huawei Nip6600 Firmware, Huawei Nip6800 Firmware, Huawei Secospace Usg6300 Firmware, Huawei Secospace Usg6500 Firmware, Huawei Secospace Usg6600 Firmware, Huawei Usg9500 Firmware.

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

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

## Is CVE-2020-9099 being exploited?

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

## Other vulnerabilities in Huawei Ips Module Firmware

- [CVE-2016-4576](https://insights.sbomify.com/CVE-2016-4576/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-37129](https://insights.sbomify.com/CVE-2021-37129/): Memory corruption in IIPS Module;NGFW Module;NIP6600;S12700;S1700;S2700;S5700;S6700;S7700;S9700;USG9500 (high 7.5)
- [CVE-2021-22320](https://insights.sbomify.com/CVE-2021-22320/): Denial of service in IPS Module;NGFW Module;NIP6600;NIP6800;Secospace USG6300;Secospace USG6500;Secospace USG6600 (high 7.5)
- [CVE-2017-15348](https://insights.sbomify.com/CVE-2017-15348/): Denial of service in IPS Module,NGFW Module,NIP6300,NIP6600,Secospace USG6300,Secospace USG6500,Secospace USG6600,USG9500, (high 7.5)
- [CVE-2017-17153](https://insights.sbomify.com/CVE-2017-17153/): Denial of service in IPS,Module,NGFW,Module,NIP6300,NIP6600,Secospace,USG6300,Secospace,USG6500,Secospace,USG6600,USG9500 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9099 is a critical authentication bypass vulnerability in Huawei Ips Module Firmware, published on 8 Jun 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-9099 in the wild and no public exploit code.

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

## Sources

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

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