CVE-2020-25152
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 · uneditedA session fixation vulnerability in the B. Braun Melsungen AG SpaceCom administrative interface Version L81/U61 and earlier, and the Data module compactplus Versions A10 and A11 allows remote attackers to hijack web sessions and escalate privileges.
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 fixation vulnerability in B. Braun SpaceCom administrative interfaces and Data module compactplus. Attackers can pre-establish or influence the session ID before user authentication, then hijack the authenticated session to gain administrative access and escalate privileges.
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= a10= a11<= l81CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Identify if B. Braun software is installedCheck system inventory or running processes for 'SpaceCom', 'Compactplus', or 'B. Braun' related services. Look for web services on common industrial protocol ports (typically HTTP/HTTPS on ports 80, 443, or custom ports used by B. Braun medical device interfaces).Affected if B. Braun SpaceCom administrative interface or Datamodule Compactplus software is present on the network.
-
Determine the installed versionAccess the administrative web interface login page and check any version information displayed, or query the device/service banner via HTTP headers or banner grabbing. Consult device documentation for version location if accessible.Affected if Version is Datamodule Compactplus a10 or a11, or SpaceCom version l81 or lower.
-
Verify administrative interface is network-accessibleConfirm the web-based administrative interface is reachable from network segments. Check firewall rules and network exposure of the management port.Affected if The administrative interface is exposed on the network without proper network segmentation.
-
Check session cookie configurationIf you can access the login page, inspect the session cookie attributes using browser developer tools or curl -I to examine Set-Cookie headers. Look for attributes such as 'Secure', 'HttpOnly', and 'SameSite'.Affected if Session cookies lack secure attributes or session ID is set before authentication (cookie present on unauthenticated login page).
-
Test for session fixation vulnerabilityAccess the login page multiple times and compare session cookie values before and after authentication. If the session ID remains constant across authentication, the vulnerability is present.Affected if Session ID does not change after successful authentication - the same ID used pre-login is retained post-login.
You are affected if B. Braun SpaceCom <= l81 or Datamodule Compactplus a10/a11 is running and the session ID remains unchanged after authentication (session fixation present).
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.
dbcve · scopedUpdate to patched versions provided by B. Braun Melsungen AG; if unavailable, implement session ID regeneration upon authentication and ensure secure session cookie attributes.
Latest SpaceCom version beyond L81/U61 and latest DataModule Compactplus version beyond A11 (obtain exact version from B. Braun)
- 1. Identify the exact SpaceCom and DataModule Compactplus software versions currently deployed in your environment
- 2. Contact B. Braun Technical Support or visit the official B. Braun website (www.bbraun.com) to obtain the latest patched version
- 3. Request and verify that the patch addresses CVE-2020-25152 specifically
- 4. Before applying in production, test the upgrade in a non-production/staging environment
- 5. Schedule maintenance window and apply the upgrade following B. Braun's official installation procedures
- 6. After upgrade, verify that session management behaves correctly (no fixed session IDs across login attempts)
- 7. Confirm the new version is no longer vulnerable to session fixation attacks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25152 — 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-2020-25152 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