CVE-2014-5433
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 unauthenticated remote attacker may be able to execute commands to view wireless account credentials that are stored in cleartext on Baxter SIGMA Spectrum Infusion System version 6.05 (model 35700BAX) with wireless battery module (WBM) version 16, which may allow an attacker to gain access the host network. 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 version 16 contains an unauthenticated remote command injection vulnerability that allows attackers to view wireless account credentials stored in cleartext, potentially enabling access to the host hospital network.
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 model numberLocate the model label on the infusion pump physical device or in the device management interface; confirm it is model 35700BAXAffected if Model number is 35700BAX (proceed to version check)
-
Check the installed firmware versionAccess the pump's system information menu or maintenance interface; record the firmware version displayedAffected if Firmware version is exactly 6.05 (this version is listed as affected)
-
Check the wireless battery module versionAccess the wireless settings or battery module information screen on the device; note the wireless battery module version numberAffected if Wireless battery module version is 16 (this specific version is listed as vulnerable)
-
Verify wireless functionality is enabledCheck the device network settings to confirm wireless communication is turned on and configuredAffected if Wireless is enabled and configured (the vulnerability exposes wireless credentials)
A user is affected if their Baxter Sigma Spectrum Infusion System is model 35700BAX with firmware version 6.05 and wireless battery module version 16, with wireless functionality enabled.
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 · scopedUpgrade to Baxter SIGMA Spectrum Infusion System Version 8, which includes both hardware and software changes to address this vulnerability. Until upgraded, network segmentation should be applied to isolate infusion pumps from critical network segments.
Sigma Spectrum Infusion System Version 8
- Verify current firmware version by accessing the Sigma Spectrum Infusion System administration interface or checking the device label (model 35700BAX, WBM version 16)
- Contact Baxter technical support to obtain the Version 8 firmware upgrade for the Sigma Spectrum Infusion System
- Schedule a maintenance window as the upgrade may require system downtime
- Follow Baxter's official upgrade procedure to install Version 8 firmware, which includes both hardware and software changes
- After upgrade, verify the system is running Version 8 and confirm wireless credentials are no longer stored in cleartext
- Test wireless connectivity and infusion system functionality to ensure proper operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation16.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $25,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5433 — 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-5433 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