# CVE-2019-6161: Auth bypass in ThinkAgile CP-SB

> Session ID reuse in Lenovo ThinkAgile CP-SB BMC allows unauthorized access to the management interface.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4jq6-g4xr-95fp

## What is CVE-2019-6161?

CVE-2019-6161 is a high-severity authentication bypass vulnerability in Lenovo ThinkAgile CP-SB, published on 26 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An internal product security audit discovered a session handling vulnerability in the web interface of ThinkAgile CP-SB (Storage Block) BMC in firmware versions prior to 1908.M. This vulnerability allows session IDs to be reused, which could provide unauthorized access to the BMC under certain circumstances. This vulnerability does not affect ThinkSystem XCC, System x IMM2, or other BMCs.

Weakness: CWE-384 (Session Fixation)

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

It affects 1 product.


Products: Lenovo Cp Storage Block Firmware.

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

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

## Is CVE-2019-6161 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6161 is a high-severity authentication bypass vulnerability in Lenovo ThinkAgile CP-SB, published on 26 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6161 in the wild and no public exploit code.

Affected product: Lenovo ThinkAgile CP-SB. 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-6161/ (Markdown: https://insights.sbomify.com/CVE-2019-6161/index.md)
```

## Sources

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

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