CVE-2019-6161
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a session handling vulnerability in the ThinkAgile CP-SB (Storage Block) BMC web interface. The flaw allows session IDs to be reused, enabling unauthorized access to the BMC under certain conditions. The vulnerability affects firmware versions prior to 1908.M and stems from improper session management where session IDs are not properly regenerated upon authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1908.mCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the ThinkAgile CP-SB BMC web interfaceIdentify whether the BMC management interface is network-accessible. Check your network inventory or scan for the BMC IP address on your internal network. The BMC web interface typically listens on port 443 or 80.Affected if The BMC web interface is directly accessible from untrusted networks (such as the internet or guest VLANs), increasing exposure to exploitation.
-
Determine the BMC firmware versionLog into the ThinkAgile CP-SB BMC web interface and navigate to the firmware version or system information page. Alternatively, use the BMC's CLI or IPMI to query the firmware version using the command: ipmitool -I lanplus -H <BMC_IP> -U <user> -P <password> fru print or check the firmware version via the web UI dashboard.Affected if The installed firmware version is earlier than 1908.m (for example, 1907.l, 1906.k, or any version prior to 1908.m).
-
Verify session regeneration behaviorAfter logging into the BMC web interface with valid credentials, note the session ID cookie or token provided. Log out, then attempt to re-authenticate using the same session ID or cookie from the previous session. Observe whether the system accepts the old session identifier without requiring new authentication.Affected if The BMC accepts and validates a previously used session ID after logout, indicating session IDs are being reused rather than regenerated upon authentication.
-
Check for session timeout configurationExamine the BMC web interface security settings to see if session timeouts are enforced. Look for session inactivity timeout values and confirm whether sessions are invalidated server-side after logout.Affected if Sessions do not expire within a reasonable timeframe (for example, less than 15-30 minutes of inactivity) or sessions remain active after client-side logout.
You are affected if your ThinkAgile CP-SB BMC firmware version is earlier than 1908.m and the web interface is accessible from your network, particularly if session IDs can be reused across authentication cycles.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1908.m
Update the ThinkAgile CP-SB BMC firmware to version 1908.M or later to obtain the vendor patch. Verify session handling behaves correctly after the update and ensure proper session termination procedures are in place.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6161 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-6161 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data