CVE Intelligence
Skip to main content

CVE-2015-3956

CVE-2015-3956 Vulnerability Analysis & Exploit Intelligence

Hospira Plum A+ Infusion System version 13.4 and prior, Plum A+3 Infusion System version 13.6 and prior, and Symbiq Infusion System, version 3.13 and prior accept drug libraries, firmware updates, pump commands, and unauthorized configuration changes from unauthenticated devices on the host network. Hospira recommends that customers close Port 20/FTP and Port 23/TELNET on the affected devices. Hospira has also released the Plum 360 Infusion System which is not vulnerable to this issue.

Published Updated Sources: cvelistV5, icscert

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

hospira

3 products listed

CVSS base

Unscored

no source published a base score

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

hospira

Products (3)

plum a infusion systemplum a 3 infusion systemsymbiq infusion system

Weakness & attack patterns

  • CWE-345

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1557.002Adversary-in-the-Middle: ARP Cache Poisoning
  • T1584.002Compromise Infrastructure: DNS Server
  • T1491Defacement

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /FTP, /TELNET.

References

1 on the record

Elsewhere on this site

  • hospiraevery CVE for this vendor
  • CWE-345other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.