CVE-2015-1012
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 · uneditedWireless keys are stored in plain text on version 5 of the Hospira LifeCare PCA Infusion System. According to Hospira, version 3 of the LifeCare PCA Infusion System is not indicated for wireless use, is not shipped with wireless capabilities, and should not be modified to be used in a wireless capacity in a clinical setting. Hospira has developed a new version of the PCS Infusion System, version 7.0 that addresses the identified vulnerabilities. Version 7.0 has Port 20/FTP and Port 23/TELNET closed by default to prevent unauthorized access.
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 confidenceWireless keys are stored in plain text on version 5 of the Hospira LifeCare PCA Infusion System, allowing attackers with network access to intercept wireless credentials. Additionally, ports 20/FTP and 23/TELNET are open by default on version 5, enabling unauthorized remote access.
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<= 5.0CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 device firmware versionAccess the Hospira LifeCare PCA Infusion System administration interface or device status screen and locate the firmware version information. This is typically found under System Settings, Device Info, or during the device boot sequence.Affected if Firmware version is 5.0 or any version lower than 5.0 (the affected range is <= 5.0)
-
Verify wireless capability statusCheck the device network configuration or wireless settings menu to determine if wireless/Wi-Fi functionality is enabled on the device.Affected if Wireless capabilities are enabled on a version 5.0 or lower firmware device, as this allows plain text wireless key storage to be exploited
-
Inspect stored wireless credentialsIf administrative access is available, examine the wireless configuration storage to verify whether network keys are stored in plain text rather than encrypted format.Affected if Wireless credentials are stored in plain text (unencrypted) format on the device
-
Scan for open FTP port 20Perform a network port scan against the device IP address targeting port 20/FTP to determine if the FTP service is exposed and accessible.Affected if Port 20/FTP is open and accessible on the device
-
Scan for open Telnet port 23Perform a network port scan against the device IP address targeting port 23/TELNET to determine if the Telnet service is exposed and accessible.Affected if Port 23/TELNET is open and accessible on the device
The environment is affected if the device runs firmware version 5.0 or lower AND has either wireless enabled (with plain text credentials) or has ports 20/FTP or 23/TELNET open and accessible on the network.
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 to version 7.0 of the PCS Infusion System, which addresses the vulnerabilities and closes ports 20/FTP and 23/TELNET by default. For version 3 units, ensure wireless capabilities are not enabled as they are not indicated for wireless use.
- Consultation12.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 $13,632.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1012 — 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-2015-1012 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