An authorization bypass exists in Lenovo XClarity Controller (XCC) versions prior to 3.08 CDI340V, 3.01 TEI392O, 1.71 PSI328N where a valid…

published 2020-02-14 6y ago modified 2026-06-17 4mo ago also EUVD-2019-15762

cvss: 4.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

Lenovo XClarity Controller (XCC) 1.71 PSI328N, 3.01 TEI392O, 3.08 CDI340V

Is CVE-2019-6195 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.8	CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N
NVD	3.1	4.8	CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N
NVD	2.0	2.1	AV:N/AC:H/Au:S/C:P/I:N/A:N

Affected products

Lenovo XClarity Controller (XCC)

Classification

Weakness

CWE-264 Permissions, Privileges, and Access Controls
CWE-269 Improper Privilege Management

References

support.lenovo.com /us/en/product_security/LEN-29116
vendor-advisory

Sources

CVE List CVE-2019-6195
NVD CVE-2019-6195

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.