CVE-2015-3955
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 · uneditedStack-based buffer overflow in Hospira LifeCare PCA Infusion System 5.0 and earlier, and possibly other versions, allows remote attackers to execute arbitrary code via unspecified vectors.
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 confidenceStack-based buffer overflow in Hospira LifeCare PCA Infusion System version 5.0 and earlier allows remote attackers to execute arbitrary code on the infusion pump device via unspecified vectors.
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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 Hospira LifeCare PCA infusion pumps on the networkReview network inventory, asset lists, or perform network discovery scanning to locate Hospira LifeCare PCA Infusion System devices. Check device MAC vendor OUI or hostname conventions if known.Affected if Hospira LifeCare PCA Infusion System devices are found on the network
-
Access the device firmware versionLog into the infusion pump management interface, device console, or consult the device administration panel to retrieve the installed firmware version. Refer to Hospira device documentation for access credentials and navigation.Affected if The firmware version displayed is 5.0 or earlier (e.g., 4.0, 3.x, etc.)
-
Verify network exposure of the deviceReview network segmentation, firewall rules, and access control lists to determine if the infusion pump has direct network access from untrusted segments or external networks.Affected if The device is accessible from network segments outside of a dedicated medical device VLAN or isolated zone
A defender is affected if their environment contains Hospira LifeCare PCA Infusion System devices running firmware version 5.0 or earlier that are 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.
From vendor dataIsolate affected infusion systems on dedicated network segments, implement compensating controls such as firewall rules limiting exposure, and contact Hospira/Pfizer for vendor-supplied patches and firmware updates.
- Consultation16.0 h
- Implementation24.0 h
- Testing20.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 $20,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3955 — 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-3955 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