# CVE-2024-11679: Information disclosure in System x3550 M5

> A local attacker with elevated privileges can read memory contents due to an input validation flaw in the TpmSetup module of Lenovo System x servers.

- **Severity:** Medium 6.7 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/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:** 11 Apr 2025
- **Updated:** 11 Apr 2025
- **Also known as:** GHSA-p8w2-9mpv-5ccm

## What is CVE-2024-11679?

CVE-2024-11679 is a medium-severity vulnerability in Lenovo System x3550 M5, published on 11 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An input validation weakness was reported in the TpmSetup module for some legacy System x server products that could allow a local attacker with elevated privileges to read the contents of memory.

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

## Which versions are affected by CVE-2024-11679?


## How do I fix CVE-2024-11679?

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

## Is CVE-2024-11679 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11679 and fix it if it is affected.

What it is: CVE-2024-11679 is a medium-severity vulnerability in Lenovo System x3550 M5, published on 11 Apr 2025. 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-2024-11679 in the wild and no public exploit code.

Affected product: Lenovo System x3550 M5. 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-2024-11679/ (Markdown: https://insights.sbomify.com/CVE-2024-11679/index.md)
```

## Sources

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

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