CVE-2020-25150
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 relative path traversal attack in the B. Braun Melsungen AG SpaceCom Version L81/U61 and earlier, and the Data module compactplus Versions A10 and A11 allows attackers with service user privileges to upload arbitrary files. By uploading a specially crafted tar file an attacker can execute arbitrary commands.
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 confidenceA relative path traversal vulnerability in B. Braun SpaceCom (L81/U61 and earlier) and Data module compactplus (A10, A11) allows authenticated service users to upload arbitrary files. By crafting a tar file with path traversal sequences (e.g., ../../../), attackers can write files outside the intended upload directory and achieve arbitrary command execution.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed B. Braun medical softwareReview installed applications or device documentation for B. Braun SpaceCom or Datamodule Compactplus software components; check device model information or software inventory listingsAffected if B. Braun SpaceCom or Datamodule Compactplus software is present on the system
-
Determine software versionAccess the device management interface or check system information/About screens for the exact version number of the B. Braun software; compare against affected versions L81 and earlier (SpaceCom) or A10/A11 (Compactplus)Affected if Version is L81 or earlier for SpaceCom, or A10/A11 for Datamodule Compactplus
-
Verify service user authentication is configuredCheck if service user accounts are enabled on the device; review user management settings or authentication configuration for service-level accessAffected if Service user accounts are active and can authenticate to the system
-
Confirm file upload functionality is accessibleLocate the firmware/software update or file upload feature in the device web interface or service management console; verify this feature accepts tar file uploadsAffected if File upload feature that accepts tar archives is exposed and accessible to authenticated service users
-
Assess network accessibility of management interfaceCheck network configuration to determine if the device management interface (HTTP/HTTPS ports) is reachable from network segments outside of isolated medical device VLANsAffected if Device management interface is accessible from non-isolated network segments
The environment is affected if B. Braun SpaceCom L81 or earlier, or Datamodule Compactplus A10/A11 is installed with service user authentication enabled and the file upload feature accessible to authenticated users.
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 dataApply vendor-provided patches/updates from B. Braun Melsungen AG; until then, minimize attack surface by restricting service user privileges and isolating affected devices on secured network segments.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25150 — 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-25150 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