CVE-2019-10959
📋 TL;DR
This vulnerability allows attackers to upload malicious firmware files to BD Alaris medical devices during firmware updates, potentially gaining unauthorized control. It affects multiple BD Alaris Gateway Workstation models and related products running vulnerable firmware versions. This could compromise medical device functionality and patient safety.
💻 Affected Systems
- BD Alaris Gateway Workstation
- Alaris GS
- Alaris GH
- Alaris CC
- Alaris TIVA
📦 What is this software?
Alaris Gateway Workstation Firmware by Bd
View all CVEs affecting Alaris Gateway Workstation Firmware →
Alaris Gateway Workstation Firmware by Bd
View all CVEs affecting Alaris Gateway Workstation Firmware →
Alaris Gateway Workstation Firmware by Bd
View all CVEs affecting Alaris Gateway Workstation Firmware →
Alaris Gateway Workstation Firmware by Bd
View all CVEs affecting Alaris Gateway Workstation Firmware →
⚠️ Risk & Real-World Impact
Worst Case
Complete device takeover allowing manipulation of medication delivery, patient data exposure, or device bricking that could directly impact patient care.
Likely Case
Unauthorized firmware installation leading to device malfunction, data theft, or disruption of medical workflows.
If Mitigated
Limited impact if network segmentation and strict access controls prevent unauthorized access to firmware update interfaces.
🎯 Exploit Status
Exploitation requires access to firmware update functionality but doesn't require authentication. No public exploit code is known.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Gateway Workstation: 1.3.2 or 1.6.1; Other products: Software Version above 2.3.6
Vendor Advisory: https://www.bd.com/en-us/support/product-security-and-privacy/product-security-bulletins/alaris-gateway-workstation-unauthorized-firmware
Restart Required: Yes
Instructions:
1. Contact BD technical support for firmware update packages. 2. Schedule maintenance window. 3. Backup device configurations. 4. Apply firmware update following BD's official procedures. 5. Verify successful update and functionality.
🔧 Temporary Workarounds
Network Segmentation
allIsolate medical devices on separate VLANs with strict firewall rules preventing unauthorized access to firmware update interfaces.
Access Control
allImplement strict authentication and authorization controls for accessing device management interfaces.
🧯 If You Can't Patch
- Implement network segmentation to isolate vulnerable devices from general network traffic
- Monitor network traffic to/from medical devices for unauthorized firmware update attempts
🔍 How to Verify
Check if Vulnerable:
Check device firmware version via device interface or management console. Compare against affected versions list.
Check Version:
Device-specific: Check via device display or management interface (no universal command)
Verify Fix Applied:
Verify firmware version shows 1.3.2, 1.6.1, or software version above 2.3.6. Test firmware update functionality with authorized procedures only.
📡 Detection & Monitoring
Log Indicators:
- Unauthorized firmware update attempts
- Unexpected device reboots
- Firmware version changes
Network Indicators:
- Unexpected traffic to firmware update ports
- Large file transfers to medical devices
SIEM Query:
source_ip IN (medical_device_subnet) AND (port:80 OR port:443) AND bytes_transferred > 100MB
🔗 References
- http://www.securityfocus.com/bid/108765
- https://ics-cert.us-cert.gov/advisories/ICSMA-19-164-01
- https://www.bd.com/en-us/support/product-security-and-privacy/product-security-bulletins/alaris-gateway-workstation-unauthorized-firmware
- http://www.securityfocus.com/bid/108765
- https://ics-cert.us-cert.gov/advisories/ICSMA-19-164-01