# CVE-2024-38511: Command injection in XClarity Controller

> Authenticated users with elevated privileges can execute arbitrary commands via crafted file uploads in Lenovo XClarity Controller.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-q6hr-rj2r-76hq

## What is CVE-2024-38511?

CVE-2024-38511 is a high-severity command injection vulnerability in Lenovo XClarity Controller, published on 26 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A privilege escalation vulnerability was discovered in an upload processing functionality of XCC that could allow an authenticated XCC user with elevated privileges to perform command injection via specially crafted file uploads.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2024-38511 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38511 is a high-severity command injection vulnerability in Lenovo XClarity Controller, published on 26 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38511 in the wild and no public exploit code.

Affected product: Lenovo XClarity Controller. 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-38511/ (Markdown: https://insights.sbomify.com/CVE-2024-38511/index.md)
```

## Sources

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

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