# CVE-2023-29057: Privilege escalation in XClarity Controller

> A local user can escalate privileges by overriding Active Directory permissions when LDAP is configured with local-first login order.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Apr 2023
- **Updated:** 30 Jan 2025
- **Also known as:** GHSA-9gph-8xxh-c4w6

## What is CVE-2023-29057?

CVE-2023-29057 is a high-severity vulnerability in Lenovo XClarity Controller, published on 28 Apr 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A valid XCC user's local account permissions overrides their active directory permissions under specific configurations. This could lead to a privilege escalation. To be vulnerable, LDAP must be configured for authentication/authorization and logins configured as “Local First, then LDAP”.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 109 products.


Products: Lenovo Thinkagile Hx1021 Firmware, Lenovo Thinkagile Hx1320 Firmware, Lenovo Thinkagile Hx1321 Firmware, Lenovo Thinkagile Hx1331 Firmware, Lenovo Thinkagile Hx1520-R Firmware, Lenovo Thinkagile Hx1521-R Firmware, Lenovo Thinkagile Hx2320-E Firmware, Lenovo Thinkagile Hx2321 Firmware, Lenovo Thinkagile Hx2330 Firmware, Lenovo Thinkagile Hx2331 Firmware, Lenovo Thinkagile Hx2720-E Firmware, Lenovo Thinkagile Hx3320 Firmware, Lenovo Thinkagile Hx3321 Firmware, Lenovo Thinkagile Hx3330 Firmware, Lenovo Thinkagile Hx3331 Firmware, Lenovo Thinkagile Hx3375 Firmware, Lenovo Thinkagile Hx3376 Firmware, Lenovo Thinkagile Hx3520-G Firmware, Lenovo Thinkagile Hx3521-G Firmware, Lenovo Thinkagile Hx3720 Firmware and 89 more.

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

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

## Is CVE-2023-29057 being exploited?

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

## Other vulnerabilities in Lenovo XClarity Controller

- [CVE-2023-0683](https://insights.sbomify.com/CVE-2023-0683/): Privilege escalation in XClarity Controller (high 8.3)
- [CVE-2022-34884](https://insights.sbomify.com/CVE-2022-34884/): Memory corruption in Lenovo XClarity Controller (high 7.2)
- [CVE-2023-29058](https://insights.sbomify.com/CVE-2023-29058/): Missing authorization in XClarity Controller (medium 6.4)
- [CVE-2023-25492](https://insights.sbomify.com/CVE-2023-25492/): Other in XClarity Controller (medium 6.3)
- [CVE-2023-29056](https://insights.sbomify.com/CVE-2023-29056/): Privilege escalation in XClarity Controller (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-29057 is a high-severity vulnerability in Lenovo XClarity Controller, published on 28 Apr 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-29057 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-2023-29057/ (Markdown: https://insights.sbomify.com/CVE-2023-29057/index.md)
```

## Sources

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

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