CVE-2014-5434
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 has a default account with hard-coded credentials used with the FTP protocol. Baxter asserts no files can be transferred to or from the WBM using this account. 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 a default account with hard-coded credentials that can be used with the FTP protocol. An unauthenticated remote attacker could potentially access this account, though Baxter claims no file transfers are possible.
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 device modelLocate the device inventory or physically inspect the Baxter SIGMA Spectrum Infusion System to confirm it is model 35700BAX. Check device labeling, asset management records, or SNMP/device discovery outputs for the model number.Affected if The device is NOT a Baxter SIGMA Spectrum model 35700BAX - different models are not affected by this specific CVE.
-
Check the firmware versionAccess the device management interface or review firmware/version documentation to determine the installed firmware version. On the SIGMA Spectrum, this is typically displayed in the system information or device status screen, or available via service documentation.Affected if The firmware version is NOT exactly 6.05. Only version 6.05 is listed as affected; other versions (including version 8 and later) are not vulnerable to this specific issue.
-
Verify if FTP is enabledCheck the device network configuration or service settings to determine if the FTP protocol is enabled or accessible on the infusion system. Review network segmentation configurations and firewall rules to see if FTP traffic (port 21) is permitted to or from the device.Affected if FTP is disabled and network access to FTP ports is blocked at the network level - the hard-coded credentials can only be exploited if FTP service is active and reachable.
You are affected only if you have a Baxter SIGMA Spectrum Infusion System model 35700BAX running firmware version 6.05 with FTP service enabled and network-accessible.
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 SIGMA Spectrum Infusion System Version 8 which incorporates hardware and software changes to address the hard-coded credential issue. Apply network segmentation and restrict FTP access as compensating controls until the upgrade can be performed.
Sigma Spectrum Infusion System Version 8
- Identify all Sigma Spectrum Infusion System devices (model 35700BAX) running firmware version 6.05 with wireless battery module (WBM) version 16 in the environment
- Contact Baxter technical support to request the Version 8 upgrade for affected devices
- Schedule a maintenance window for the upgrade process, ensuring patient safety protocols are followed
- Upgrade the affected Sigma Spectrum Infusion System devices to Version 8 following Baxter's official upgrade documentation
- Verify the upgrade was successful and confirm the hard-coded FTP credentials are no longer present
- Document the remediation actions for compliance and audit purposes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5434 — 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-5434 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