# CVE-2017-12542: Auth bypass in Integrated Lights-out 4 (iLO 4)

> Attackers can bypass authentication and execute arbitrary code on HPE iLO 4 management controllers, requiring immediate firmware upgrades.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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:** 15 Feb 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-7m3v-cw5q-g499

## What is CVE-2017-12542?

CVE-2017-12542 is a critical authentication bypass vulnerability in Hewlett Packard Enterprise Integrated Lights-out 4 (iLO 4), published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A authentication bypass and execution of code vulnerability in HPE Integrated Lights-out 4 (iLO 4) version prior to 2.53 was found.

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

It affects 1 product.


Products: Hp Integrated Lights-Out 4 Firmware.

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

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

## Is CVE-2017-12542 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-12542 exists.

Public exploit code:

- Test and exploit for CVE-2017-12542 (github_poc): https://github.com/skelsec/CVE-2017-12542
- Scan a list of given IP's for CVE-2017-12542 (github_poc): https://github.com/sk1dish/ilo4-rce-vuln-scanner
- HP iLO 4 1.00-2.50 Authentication Bypass Administrator Account Creation (metasploit)
- HPE iLO 4 < 2.53 - Add New Administrator User (exploitdb)
- This script checks if an HP iLO server is vulnerable and can add an admin user (github_poc): https://github.com/VijayShankar22/CVE-2017-12542
- Proof-of-concept exploit for CVE-2017-12542, an authentication bypass vulnerability in HP iLO. Allows vulnerability detection and unauthorized account creation on affected systems (github_poc): https://github.com/Gill-Singh-A/CVE-2017-12542-Exploit

## Other vulnerabilities in Hewlett Packard Enterprise Integrated Lights-out 4 (iLO 4)

- [CVE-2019-11982](https://insights.sbomify.com/CVE-2019-11982/): Cross-site scripting in HPE iLO4 and HPE iLO5 (high 8.3)
- [CVE-2018-7101](https://insights.sbomify.com/CVE-2018-7101/): Denial of service in HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers, HPE Integrated Lights-Out 4 (iLO 4) (high 7.5)
- [CVE-2018-7078](https://insights.sbomify.com/CVE-2018-7078/): Code injection in HPE Integrated Lights-Out 4 (iLO 4), HPE Integrated Lights-Out 5 (iLO 5) (high 7.2)
- [CVE-2019-11983](https://insights.sbomify.com/CVE-2019-11983/): Memory corruption in HPE iLO4 and HPE iLO5 (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12542 is a critical authentication bypass vulnerability in Hewlett Packard Enterprise Integrated Lights-out 4 (iLO 4), published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-12542 exists.

Affected product: Hewlett Packard Enterprise Integrated Lights-out 4 (iLO 4). 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-12542/ (Markdown: https://insights.sbomify.com/CVE-2017-12542/index.md)
```

## Sources

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

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