# CVE-2018-7105: Code injection in HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers, HPE Integrated Lights-Out 4 (iLO 4), HPE Integrated Lights-Out 3 (iLO 3)

> Remote attackers can execute arbitrary code on HPE iLO firmware, leading to information disclosure and system compromise.

- **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:** 27 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7p7j-2gc7-ww6f

## What is CVE-2018-7105?

CVE-2018-7105 is a high-severity code injection vulnerability in Hewlett Packard Enterprise HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers, HPE Integrated Lights-Out 4 (iLO 4), HPE Integrated Lights-Out 3 (iLO 3), published on 27 Sep 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A security vulnerability in HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers prior to v1.35, HPE Integrated Lights-Out 4 (iLO 4) prior to v2.61, HPE Integrated Lights-Out 3 (iLO 3) prior to v1.90 could be remotely exploited to execute arbitrary code leading to disclosure of information.

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

It affects 3 products.


Products: Hp Integrated Lights-Out 3 Firmware, Hp Integrated Lights-Out 4 Firmware, Hp Integrated Lights-Out 5 Firmware.

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

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

## Is CVE-2018-7105 being exploited?

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

## Other vulnerabilities in Hewlett Packard Enterprise HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers, HPE Integrated Lights-Out 4 (iLO 4), HPE Integrated Lights-Out 3 (iLO 3)

- [CVE-2013-2338](https://insights.sbomify.com/CVE-2013-2338/): Code injection in n/a (critical 10.0)
- [CVE-2016-4375](https://insights.sbomify.com/CVE-2016-4375/): Information disclosure in n/a (critical 9.8)
- [CVE-2012-3271](https://insights.sbomify.com/CVE-2012-3271/): Information disclosure in n/a (critical 9.3)
- [CVE-2018-7093](https://insights.sbomify.com/CVE-2018-7093/): Denial of service in iLO 5 for HPE Gen10 Servers, iLO 4, iLO 3, Moonshot Chassis Management Firmware, Moonshot Component Packs for HPE ProLiant m510 and m710x server cartridges (high 8.6)
- [CVE-2017-8987](https://insights.sbomify.com/CVE-2017-8987/): Denial of service in HPE Integrated Lights-Out 3 (iLO 3) (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7105 is a high-severity code injection vulnerability in Hewlett Packard Enterprise HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers, HPE Integrated Lights-Out 4 (iLO 4), HPE Integrated Lights-Out 3 (iLO 3), published on 27 Sep 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7105 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers, HPE Integrated Lights-Out 4 (iLO 4), HPE Integrated Lights-Out 3 (iLO 3). 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-7105/ (Markdown: https://insights.sbomify.com/CVE-2018-7105/index.md)
```

## Sources

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

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