# CVE-2021-39976: Privilege escalation in CloudEngine 5800

> An authenticated local attacker can exploit missing privilege restrictions on CloudEngine 5800 switches to gain higher privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qjh4-6fwh-rj27

## What is CVE-2021-39976?

CVE-2021-39976 is a high-severity vulnerability in CloudEngine 5800, published on 23 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is a privilege escalation vulnerability in CloudEngine 5800 V200R020C00SPC600. Due to lack of privilege restrictions, an authenticated local attacker can perform specific operation to exploit this vulnerability. Successful exploitation may cause the attacker to obtain a higher privilege.

## Which versions are affected by CVE-2021-39976?

It affects 1 product.


Products: Huawei Cloudengine 5800 Firmware.

## How do I fix CVE-2021-39976?

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

## Is CVE-2021-39976 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-39976 and fix it if it is affected.

What it is: CVE-2021-39976 is a high-severity vulnerability in CloudEngine 5800, published on 23 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-39976 in the wild and no public exploit code.

Affected product: CloudEngine 5800. 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-2021-39976/ (Markdown: https://insights.sbomify.com/CVE-2021-39976/index.md)
```

## Sources

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

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