# CVE-2022-34888: Server-side request forgery in Lenovo XClarity Controller

> Authenticated users can abuse the Remote Mount feature to access internal services that are normally inaccessible, bypassing network restrictions.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2023
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-8pjh-hch3-85g6

## What is CVE-2022-34888?

CVE-2022-34888 is a low-severity server-side request forgery vulnerability in Lenovo XClarity Controller, published on 30 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Remote Mount feature can potentially be abused by valid, authenticated users to make connections to internal services that may not normally be accessible to users. Internal service access controls, as applicable, remain in effect.

Weakness: CWE-697 (Incorrect Comparison), CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2022-34888?

It affects 98 products.


Products: Lenovo Thinkagile Hx1021 Firmware, Lenovo Thinkagile Hx1320 Firmware, Lenovo Thinkagile Hx1321 Firmware, Lenovo Thinkagile Hx1520-R Firmware, Lenovo Thinkagile Hx1521-R Firmware, Lenovo Thinkagile Hx2320-E Firmware, Lenovo Thinkagile Hx2321 Firmware, Lenovo Thinkagile Hx2720-E Firmware, Lenovo Thinkagile Hx3320 Firmware, Lenovo Thinkagile Hx3321 Firmware, Lenovo Thinkagile Hx3375 Firmware, Lenovo Thinkagile Hx3376 Firmware, Lenovo Thinkagile Hx3520-G Firmware, Lenovo Thinkagile Hx3521-G Firmware, Lenovo Thinkagile Hx3720 Firmware, Lenovo Thinkagile Hx3721 Firmware, Lenovo Thinkagile Hx5520-C Firmware, Lenovo Thinkagile Hx5520 Firmware, Lenovo Thinkagile Hx5521-C Firmware, Lenovo Thinkagile Hx5521 Firmware and 78 more.

## How do I fix CVE-2022-34888?

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

## Is CVE-2022-34888 being exploited?

There is no known exploitation of CVE-2022-34888 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-2023-29057](https://insights.sbomify.com/CVE-2023-29057/): Privilege escalation in XClarity Controller (high 7.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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34888 and fix it if it is affected.

What it is: CVE-2022-34888 is a low-severity server-side request forgery vulnerability in Lenovo XClarity Controller, published on 30 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34888 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-2022-34888/ (Markdown: https://insights.sbomify.com/CVE-2022-34888/index.md)
```

## Sources

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

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