# CVE-2018-7120: Privilege escalation in HPE Virtual Connect SE 16Gb Fibre Channel Module for HPE Synergy

> Local or remote attackers can gain unauthorized elevated privileges on HPE Virtual Connect SE Fibre Channel Modules.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 10 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rcp6-cg59-w8qx

## What is CVE-2018-7120?

CVE-2018-7120 is a critical vulnerability in HPE Virtual Connect SE 16Gb Fibre Channel Module for HPE Synergy, published on 10 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security vulnerability in the HPE Virtual Connect SE 16Gb Fibre Channel Module for HPE Synergy running firmware 5.00.50, which is part of the HPE Synergy Custom SPP 2018.11.20190205, could allow local or remote unauthorized elevation of privilege.

## Which versions are affected by CVE-2018-7120?

It affects 1 product.


Products: Hp Synergy Firmware.

## How do I fix CVE-2018-7120?

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

## Is CVE-2018-7120 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7120 and fix it if it is affected.

What it is: CVE-2018-7120 is a critical vulnerability in HPE Virtual Connect SE 16Gb Fibre Channel Module for HPE Synergy, published on 10 May 2019. 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-2018-7120 in the wild and no public exploit code.

Affected product: HPE Virtual Connect SE 16Gb Fibre Channel Module for HPE Synergy. 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-2018-7120/ (Markdown: https://insights.sbomify.com/CVE-2018-7120/index.md)
```

## Sources

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

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