# CVE-2017-8187: Privilege escalation in FusionSphere OpenStack

> An attacker with high privileges can obtain other users' certificates, leading to privilege escalation in Huawei FusionSphere OpenStack.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-98fr-rpfg-wcvp

## What is CVE-2017-8187?

CVE-2017-8187 is a high-severity vulnerability in Huawei Technologies Co., Ltd. FusionSphere OpenStack, published on 20 Mar 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Huawei FusionSphere OpenStack V100R006C00SPC102(NFV) has a privilege escalation vulnerability. Due to improper privilege restrictions, an attacker with high privilege may obtain the other users' certificates. Successful exploit may cause privilege escalation.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-8187?

It affects 1 product.


Products: Huawei Fusionsphere Openstack Firmware.

## How do I fix CVE-2017-8187?

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

## Is CVE-2017-8187 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8187 and fix it if it is affected.

What it is: CVE-2017-8187 is a high-severity vulnerability in Huawei Technologies Co., Ltd. FusionSphere OpenStack, published on 20 Mar 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-8187 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. FusionSphere OpenStack. 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-2017-8187/ (Markdown: https://insights.sbomify.com/CVE-2017-8187/index.md)
```

## Sources

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

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