# CVE-2019-6195: Auth bypass in XClarity Controller (XCC)

> A lesser-privileged user can gain read-only access to higher-privileged information in Lenovo XClarity Controller under specific LDAP authentication configurations.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **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:** 14 Feb 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xhgx-q9xg-fg3q

## What is CVE-2019-6195?

CVE-2019-6195 is a medium-severity authentication bypass vulnerability in Lenovo XClarity Controller (XCC), published on 14 Feb 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An authorization bypass exists in Lenovo XClarity Controller (XCC) versions prior to 3.08 CDI340V, 3.01 TEI392O, 1.71 PSI328N where a valid authenticated user with lesser privileges may be granted read-only access to higher-privileged information if 1) “LDAP Authentication Only with Local Authorization” mode is configured and used by XCC, and 2) a lesser privileged user logs into XCC within 1 minute of a higher privileged user logging out. The authorization bypass does not exist when “Local Authentication and Authorization” or “LDAP Authentication and Authorization” modes are configured and used by XCC.

Weakness: CWE-269 (Improper Privilege Management), CWE-264

## Which versions are affected by CVE-2019-6195?

It affects 1 product.


Products: Lenovo Xclarity Controller.

## How do I fix CVE-2019-6195?

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

## Is CVE-2019-6195 being exploited?

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

## Other vulnerabilities in Lenovo XClarity Controller (XCC)

- [CVE-2019-6187](https://insights.sbomify.com/CVE-2019-6187/): Other in Lenovo XClarity Controller (XCC) (medium 6.5)
- [CVE-2021-3473](https://insights.sbomify.com/CVE-2021-3473/): Information disclosure in XClarity Controller (XCC) (medium 4.5)
- [CVE-2021-3956](https://insights.sbomify.com/CVE-2021-3956/): Auth bypass in XClarity Controller (XCC) (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6195 and fix it if it is affected.

What it is: CVE-2019-6195 is a medium-severity authentication bypass vulnerability in Lenovo XClarity Controller (XCC), published on 14 Feb 2020. 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-2019-6195 in the wild and no public exploit code.

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

## Sources

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

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