# CVE-2018-2566: Missing authorization in SSM - (hot-tamale) ILOM: Integrated Lights Out Manager

> Low-privileged attackers can modify or read critical ILOM data via the remote console, requiring user interaction.

- **Severity:** High 7.7 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jan 2018
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-mxp2-5233-73gr

## What is CVE-2018-2566?

CVE-2018-2566 is a high-severity missing authorization vulnerability in Oracle Corporation SSM - (hot-tamale) ILOM: Integrated Lights Out Manager, published on 18 Jan 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Integrated Lights Out Manager (ILOM) component of Oracle Sun Systems Products Suite (subcomponent: Remote Console Application). Supported versions that are affected are 3.x and 4.x. Difficult to exploit vulnerability allows low privileged attacker with network access via TLS to compromise Integrated Lights Out Manager (ILOM). Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Integrated Lights Out Manager (ILOM), attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Integrated Lights Out Manager (ILOM) accessible data as well as unauthorized access to critical data or complete access to all Integrated Lights Out Manager (ILOM) accessible data. CVSS 3.0 Base Score 7.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N).

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

It affects 1 product.


Products: Oracle Integrated Lights Out Manager Firmware.

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

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

## Is CVE-2018-2566 being exploited?

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

## Other vulnerabilities in Oracle Corporation SSM - (hot-tamale) ILOM: Integrated Lights Out Manager

- [CVE-2016-5453](https://insights.sbomify.com/CVE-2016-5453/): Other in n/a (critical 9.8)
- [CVE-2016-5457](https://insights.sbomify.com/CVE-2016-5457/): Other in n/a (high 8.8)
- [CVE-2016-5445](https://insights.sbomify.com/CVE-2016-5445/): Other in n/a (high 8.3)
- [CVE-2016-3481](https://insights.sbomify.com/CVE-2016-3481/): Denial of service in n/a (high 7.7)
- [CVE-2016-5447](https://insights.sbomify.com/CVE-2016-5447/): Other in n/a (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2566 is a high-severity missing authorization vulnerability in Oracle Corporation SSM - (hot-tamale) ILOM: Integrated Lights Out Manager, published on 18 Jan 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-2566 in the wild and no public exploit code.

Affected product: Oracle Corporation SSM - (hot-tamale) ILOM: Integrated Lights Out Manager. 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-2566/ (Markdown: https://insights.sbomify.com/CVE-2018-2566/index.md)
```

## Sources

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

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