CVE-2020-25154
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 · uneditedAn open redirect vulnerability in the administrative interface of the B. Braun Melsungen AG SpaceCom device Version L81/U61 and earlier, and the Data module compactplus Versions A10 and A11 allows attackers to redirect users to malicious websites.
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 confidenceAn open redirect vulnerability exists in the administrative web interface of B. Braun SpaceCom devices (versions L81/U61 and earlier) and Data module compactplus (versions A10 and A11). Attackers can manipulate the application to redirect users to attacker-controlled malicious websites by injecting untrusted destinations into redirect parameters, potentially leading to phishing attacks or malware delivery.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 B. Braun medical devices on the networkScan the network for devices displaying B. Braun identifiers or run device discovery tools to locate SpaceCom and Data module compactplus unitsAffected if B. Braun SpaceCom or Data module compactplus devices are found on the network
-
Determine SpaceCom firmware versionAccess the device administrative interface and navigate to the system information or firmware version page, or query the device via SNMP or vendor management tools if availableAffected if The displayed version is L81 or any version lower than L81 (for example, L80, L72, etc.)
-
Determine Data module compactplus versionAccess the device administrative interface and locate the version information in system settings or firmware detailsAffected if The displayed version is A10 or A11
-
Verify administrative web interface is exposedCheck if the web-based administrative interface is accessible from network segments outside of isolated medical device zones; attempt to reach the login page via HTTP/HTTPS on typical web portsAffected if The administrative interface is reachable from network segments that are not specifically segmented for medical devices
-
Test for open redirect behaviorIf administrative access is available, locate redirect parameters in the interface (such as logout or navigation links) and modify the redirect URL parameter to an external domain (for example, change the destination to example.com); observe if the application allows redirection to the arbitrary domainAffected if The application redirects to the attacker-controlled domain without proper validation, confirming the open redirect vulnerability is present
A user is affected if their environment contains B. Braun SpaceCom devices at version L81 or lower, or Data module compactplus at version A10 or A11, and the administrative web interface is accessible and exhibits open redirect behavior when redirect parameters are manipulated.
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-supplied patches when available; until then, implement network segmentation to isolate medical devices and deploy URL filtering/monitoring to detect and block suspicious redirect attempts in the administrative interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25154 — 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-25154 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