CVE-2017-6018
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 issue was discovered in B. Braun Medical SpaceCom module, which is integrated into the SpaceStation docking station: SpaceStation with SpaceCom module (integrated as part number 8713142U), software versions prior to Version 012U000040, and SpaceStation (part number 8713140U) with installed SpaceCom module (part number 8713160U), software versions prior to Version 012U000040. The web server of the affected product accepts untrusted input which could allow attackers to redirect the request to an unintended URL contained within untrusted input.
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 B. Braun Medical SpaceCom module web server. The affected web server accepts untrusted input (likely a redirect parameter) without proper validation, allowing attackers to craft malicious URLs that redirect users to attacker-controlled websites.
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 dataall versionsCVSS 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.0/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 Station device on networkScan network for B. Braun Medical devices or review asset inventory for 'Bbraun Station' or 'SpaceCom' entries. The device may identify itself via SNMP, mDNS, or HTTP headers containing 'B. Braun' or 'SpaceCom' strings.Affected if B. Braun Station with SpaceCom module is present on the network
-
Locate SpaceCom module web serverIdentify open HTTP/HTTPS ports on the B. Braun Station device. Common ports include 80, 443, or vendor-assigned ports. Check device documentation for the expected web server port.Affected if The SpaceCom web interface is accessible via network (even on internal network)
-
Determine firmware versionAccess the SpaceCom web interface and navigate to system information, settings, or status pages to locate the firmware version. Alternatively, check device management console or SNMP sysDescr for version string.Affected if Firmware version can be determined as Bbraun Station (all versions are affected)
-
Inspect redirect functionalityReview web application for any redirect or URL parameters (such as 'url=', 'redirect=', 'next=', 'dest='). Attempt to inject an external domain (for example, append '?redirect=https://example.com') to any parameter and observe if an HTTP 3xx redirect to the external domain occurs.Affected if The web application performs redirects based on unvalidated user-supplied parameters
You are affected if you have a B. Braun Station with SpaceCom module accessible on your network and the web interface allows external redirects via URL parameters without validation.
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 dataUpgrade SpaceCom module software to Version 012U000040 or later per vendor guidance. Additionally, implement strict input validation on any redirect parameters to ensure only trusted destinations are allowed.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.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,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6018 — 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-2017-6018 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