CVE-2020-25160
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 · uneditedImproper access controls in the B. Braun Melsungen AG SpaceCom Version L81/U61 and earlier, and the Data module compactplus Versions A10 and A11 enables attackers to extract and tamper with the devices network configuration.
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 confidenceImproper access controls in B. Braun SpaceCom (L81/U61 and earlier) and Data module compactplus (A10, A11) allow authenticated or positioned attackers to extract and modify network configuration settings, potentially enabling further compromise or device manipulation.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
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 device model and firmware versionLocate the device label or access the device management interface to determine if the unit is a B. Braun Data module Compactplus (model A10 or A11) or a SpaceCom unit. Note the firmware version reported.Affected if The device is a Compactplus A10/A11 or a SpaceCom with firmware version L81 or earlier (including U61).
-
Verify network management interface accessibilityFrom a network perspective, determine if the device management interface (typically HTTP/HTTPS ports used for device configuration) is reachable from network segments that contain untrusted devices or users. Use port scanning or network access control lists to test this.Affected if The device management interface is accessible from untrusted network segments without additional authentication barriers.
-
Check authentication enforcement on network configurationAttempt to access the device network configuration pages or API endpoints without providing credentials, or with invalid credentials, to verify whether authentication is properly enforced.Affected if Network configuration settings can be viewed or modified without successful authentication.
-
Inspect access control configurationIf accessible, review the device security or access control settings to confirm whether authentication is enabled and required for network configuration changes.Affected if Authentication is disabled, optional, or improperly enforced for network configuration features.
The environment is affected if B. Braun Compactplus (A10/A11) or SpaceCom (L81 or earlier) devices have their network management interfaces accessible without proper authentication enforcement.
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 dataIsolate affected devices on restricted network segments, implement strong authentication for management interfaces, and coordinate with B. Braun for patched firmware versions if available.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25160 — 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-25160 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