CVE-2020-25164
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 vulnerability in the B. Braun Melsungen AG SpaceCom Version L81/U61 and earlier, and the Data module compactplus Versions A10 and A11 allows attackers to recover user credentials of the administrative interface.
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 · moderate confidenceB. Braun SpaceCom and Data module compactplus devices contain a vulnerability allowing credential recovery for the administrative interface. Attackers can obtain user credentials, potentially enabling unauthorized access to configure infusion pump settings and other patient-critical parameters.
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
- 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.
-
Identify the device model and firmware versionAccess the device's system information page or check the device label/metadata. For SpaceCom, look for version L81 or earlier in the admin interface under System > Info or on the physical device label. For Datamodule Compactplus, check for version A10 or A11 in the same locations.Affected if The device is a B. Braun SpaceCom with version L81 or lower, or a Datamodule Compactplus with version exactly A10 or A11.
-
Confirm the specific model variantVerify whether the device is a SpaceCom unit or a Datamodule Compactplus. Check the device identification string or model number displayed in the administrative interface or on the physical unit.Affected if The device is specifically a B. Braun SpaceCom or B. Braun Datamodule Compactplus matching the version criteria.
-
Determine if administrative interface is network-accessibleCheck network configuration settings in the device admin panel. Look for exposed HTTP/HTTPS ports (typically 80/443 or custom admin ports). Verify if the admin interface is accessible from network segments outside of restricted clinical networks.Affected if The administrative web interface is accessible from network segments beyond isolated clinical device networks, increasing exposure to credential theft.
-
Review admin interface authentication mechanismIn the administrative interface, examine the login page and authentication configuration. Note if credentials are transmitted without encryption or if there are endpoints that may leak credential information.Affected if The admin interface allows credential retrieval through insecure authentication methods or exposes credential-related responses.
A user is affected if their B. Braun SpaceCom device runs version L81 or earlier, or their Datamodule Compactplus runs exactly version A10 or A11, AND the administrative interface is network-accessible to potential attackers.
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 dataUpdate SpaceCom to version newer than L81/U61 and Data module compactplus to version newer than A11. Implement network segmentation to restrict access to administrative interfaces and follow B. Braun's patch deployment guidance for medical devices.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25164 — 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-25164 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