# CVE-2023-49144: Information disclosure in Intel(R) Server Platforms

> A privileged local attacker can exploit an out-of-bounds read in Intel Server Platform firmware to disclose sensitive information.

- **Severity:** High 8.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2024
- **Updated:** 16 Aug 2024
- **Also known as:** GHSA-jm96-wx5c-hr7m

## What is CVE-2023-49144?

CVE-2023-49144 is a high-severity vulnerability in Intel(R) Server Platforms, published on 14 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out of bounds read in OpenBMC Firmware for some Intel(R) Server Platforms before versions egs-1.15-0, bhs-0.27 may allow a privileged user to potentially enable information disclosure via local access.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2023-49144?


## How do I fix CVE-2023-49144?

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

## Is CVE-2023-49144 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49144 and fix it if it is affected.

What it is: CVE-2023-49144 is a high-severity vulnerability in Intel(R) Server Platforms, published on 14 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-49144 in the wild and no public exploit code.

Affected product: Intel(R) Server Platforms. 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-2023-49144/ (Markdown: https://insights.sbomify.com/CVE-2023-49144/index.md)
```

## Sources

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

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