dbcve.org
Datamodule CompactplusOperating system · Bbraun

CVE-2020-25162

HIGH · 7.5 CVSS v3.1 Published 2022-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A XPath injection vulnerability in the B. Braun Melsungen AG SpaceCom Version L81/U61 and earlier, and the Data module compactplus Versions A10 and A11 allows unauthenticated remote attackers to access sensitive information 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 · moderate confidence

This is an XPath injection vulnerability in B. Braun Melsungen AG's SpaceCom (versions L81/U61 and earlier) and Data module compactplus (versions A10 and A11) medical device software. The flaw allows unauthenticated remote attackers to inject malicious XPath queries to access sensitive information and escalate privileges.

MitigationImplement proper input validation and parameterized/prepared XPath queries to prevent injection attacks. Since this is a medical device, coordinate with the vendor for official patches and ensure any changes comply with medical device regulatory requirements.

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
Datamodule CompactplusOperating system
Affected:= a10= a11
SpacecomOperating system
Affected:<= l81

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SpaceCom software version
    Locate the SpaceCom application on the system and retrieve its version information. This is typically visible in the software's about panel, installation directory, or system information interface.
    Affected if The version is L81, U61, or any version earlier than L81/U61 (e.g., L80, L72, etc.)
  2. Identify Data module compactplus version
    Locate the Data module compactplus application and retrieve its version number from the software's info panel, installation metadata, or system registry entries if applicable.
    Affected if The version is exactly A10 or exactly A11 (these are the only affected versions for this product).
  3. Determine if XPath query interface is enabled
    Check the SpaceCom or Data module compactplus configuration settings to see if the XPath query functionality or web service interface is enabled and accessible.
    Affected if The XPath interface is exposed and accepts user-supplied input without proper sanitization mechanisms in place.
  4. Assess network exposure of the service
    Review network configuration and firewall rules to determine if the SpaceCom or Data module compactplus service is accessible from network segments outside the intended medical device network.
    Affected if The affected service is reachable from unauthenticated network locations, allowing external attackers to send malicious XPath queries.

Your environment is affected if you are running SpaceCom version L81/U61 or earlier, or Data module compactplus version A10 or A11, with the XPath interface accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and parameterized/prepared XPath queries to prevent injection attacks. Since this is a medical device, coordinate with the vendor for official patches and ensure any changes comply with medical device regulatory requirements.

Recommended fix Moderate confidence

Contact B. Braun for vendor-specific patched firmware (fixed version numbers not publicly disclosed in advisory)

  1. Contact B. Braun customer support or technical service to request the patched firmware version for your SpaceCom and/or DataModule Compactplus device
  2. Confirm your current firmware version by accessing the device management interface or checking the device label
  3. Request and apply the vendor-provided security patch or firmware update that addresses CVE-2020-25162
  4. After patching, verify the XPath injection vulnerability is resolved by confirming the patch version is installed
  5. Ensure network segmentation and access controls are in place as additional defense-in-depth measures while awaiting the patch
Caveat Firmware updates on medical devices may require vendor supervision and could affect device calibration or settings - coordinate with B. Braun technical support

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Datamodule Compactplus Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-25162 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-25162 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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