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

> Unauthenticated attackers can modify, read, or disrupt Oracle ILOM data via network access due to missing authorization checks.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2018
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-m4r5-cr22-679m

## What is CVE-2018-2568?

CVE-2018-2568 is a high-severity missing authorization vulnerability in Oracle Corporation SSM - (hot-tamale) ILOM: Integrated Lights Out Manager, published on 18 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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. Easily exploitable vulnerability allows unauthenticated attacker with network access via TLS to compromise Integrated Lights Out Manager (ILOM). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Integrated Lights Out Manager (ILOM) accessible data as well as unauthorized read access to a subset of Integrated Lights Out Manager (ILOM) accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Integrated Lights Out Manager (ILOM). CVSS 3.0 Base Score 7.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L).

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

It affects 1 product.


Products: Oracle Integrated Lights Out Manager Firmware.

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

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

## Is CVE-2018-2568 being exploited?

There is no known exploitation of CVE-2018-2568 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-2018-2566](https://insights.sbomify.com/CVE-2018-2566/): Missing authorization in SSM - (hot-tamale) ILOM: Integrated Lights Out Manager (high 7.7)
- [CVE-2016-3481](https://insights.sbomify.com/CVE-2016-3481/): Denial of service in n/a (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2568 is a high-severity missing authorization vulnerability in Oracle Corporation SSM - (hot-tamale) ILOM: Integrated Lights Out Manager, published on 18 Jan 2018. 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-2568 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-2568/ (Markdown: https://insights.sbomify.com/CVE-2018-2568/index.md)
```

## Sources

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

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