# CVE-2018-7118: A local access restriction bypass vulnerability was identified in HPE Service Pack for ProLiant (SPP) Bundled Software earlier than version 2018.09.0.


- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Apr 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9gpx-9fh8-gjp6

## What is CVE-2018-7118?

CVE-2018-7118 is a high-severity vulnerability in HPE Service Pack for Proliant (HPE SPP), published on 9 Apr 2019. 

### Official description

A local access restriction bypass vulnerability was identified in HPE Service Pack for ProLiant (SPP) Bundled Software earlier than version 2018.09.0.

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

It affects 1 product.


Products: Hp Service Pack for Proliant.

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

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

## Is CVE-2018-7118 being exploited?

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

## Other vulnerabilities in HPE Service Pack for Proliant (HPE SPP)

- [CVE-2020-7135](https://insights.sbomify.com/CVE-2020-7135/): Code injection in HPE Business Critical Hard Drives (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7118 is a high-severity vulnerability in HPE Service Pack for Proliant (HPE SPP), published on 9 Apr 2019. 
Exploitation: There is no known exploitation of CVE-2018-7118 in the wild and no public exploit code.

Affected product: HPE Service Pack for Proliant (HPE SPP). 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-7118/ (Markdown: https://insights.sbomify.com/CVE-2018-7118/index.md)
```

## Sources

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

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