# CVE-2024-8059: Information disclosure in HX Enclosure Certified Node (ThinkAgile) XCC

> Attackers with log access can view IPMI credentials in audit logs when usernames are 16 characters long.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2024
- **Updated:** 13 Sep 2024
- **Also known as:** GHSA-2hgx-34f4-hp3q

## What is CVE-2024-8059?

CVE-2024-8059 is a medium-severity vulnerability in Lenovo HX Enclosure Certified Node (ThinkAgile) XCC, published on 13 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IPMI credentials may be captured in XCC audit log entries when the account username length is 16 characters.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2024-8059 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8059 is a medium-severity vulnerability in Lenovo HX Enclosure Certified Node (ThinkAgile) XCC, published on 13 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8059 in the wild and no public exploit code.

Affected product: Lenovo HX Enclosure Certified Node (ThinkAgile) XCC. 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-8059/ (Markdown: https://insights.sbomify.com/CVE-2024-8059/index.md)
```

## Sources

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

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