CVE-2014-5432
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 · uneditedBaxter SIGMA Spectrum Infusion System version 6.05 (model 35700BAX) with wireless battery module (WBM) version 16 is remotely accessible via Port 22/SSH without authentication. A remote attacker may be able to make unauthorized configuration changes to the WBM, as well as issue commands to access account credentials and shared keys. Baxter asserts that this vulnerability only allows access to features and functionality on the WBM and that the SIGMA Spectrum infusion pump cannot be controlled from the WBM. Baxter has released a new version of the SIGMA Spectrum Infusion System, Version 8, which incorporates hardware and software changes.
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 · high confidenceThe Baxter SIGMA Spectrum Infusion System version 6.05 (model 35700BAX) with wireless battery module (WBM) version 16 exposes SSH (Port 22) without authentication, allowing remote attackers to make unauthorized configuration changes to the WBM and retrieve account credentials and shared keys. While the vendor states the infusion pump itself cannot be controlled via this vulnerability, the exposure of credentials and keys poses a significant security risk.
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= 6.05CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 the Baxter Sigma Spectrum device on the networkUse network scanning tools (such as Nmap) or check device inventory/monitoring systems to identify devices with model identifier 35700BAX or the SIGMA Spectrum Infusion System hostname/vendor fingerprintAffected if The device is confirmed to be a Baxter Sigma Spectrum Infusion System model 35700BAX
-
Check the installed firmware versionIf you have administrative access or can query the device management interface, retrieve the firmware version from the system information or device status pageAffected if The firmware version is exactly 6.05
-
Scan for open SSH port 22 on the devicePerform a port scan (e.g., nmap -p 22 <target_ip>) against the device IP address to check if TCP port 22 is exposed and accessibleAffected if Port 22 is open and reachable on the device
-
Verify wireless battery module versionIf accessible through the device management interface or SNMP, check the wireless battery module (WBM) version informationAffected if WBM version 16 is installed
-
Test for unauthenticated SSH accessAttempt an SSH connection (e.g., ssh -v <target_ip>) without providing credentials to verify if the service allows unauthenticated accessAffected if SSH connects successfully without requiring any authentication credentials
You are affected if you have a Baxter Sigma Spectrum Infusion System model 35700BAX running firmware version 6.05 with an accessible SSH service on port 22 that permits unauthenticated access.
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.
dbcve · scopedBaxter has released Version 8 of the SIGMA Spectrum Infusion System with hardware and software changes to address this vulnerability. Organizations should upgrade to the new version and, as an interim measure, restrict network access to Port 22 on affected devices if upgrading is not immediately feasible.
Sigma Spectrum Infusion System Version 8
- Upgrade the Baxter SIGMA Spectrum Infusion System from version 6.05 to Version 8 to remediate the unauthenticated SSH vulnerability
- Contact Baxter technical support to obtain the Version 8 upgrade package and scheduling
- Follow Baxter's official upgrade procedure for the Sigma Spectrum Infusion System, including any hardware module replacements if required
- After upgrading, verify that Port 22/SSH now requires authentication before access is granted
- Confirm that unauthorized configuration changes to the wireless battery module (WBM) are no longer possible without valid credentials
- Document the upgrade in the device's maintenance records per organizational change management procedures
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2014-5432 — 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-2014-5432 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