Medtronic 9790, 2090 CareLink, and 29901 Encore Programmers
ICSA： ICS Medical Advisory (ICSMA-18-347-01)
1. EXECUTIVE SUMMARY
- CVSS v3 4.6
- ATTENTION: Low skill level to exploit
- Vendor: Medtronic
- Equipment: 9790 CareLink Programmer, 2090 CareLink Programmer, 29901 Encore Programmer
- Vulnerability: Missing Encryption of Sensitive Data
2. RISK EVALUATION
As part of the intended functionality of this device, it may store protected health information (PHI) or personally identifiable information (PII). Successful exploitation of the vulnerability may allow an attacker with physical access to an affected programmer to access PHI or PII stored on the device.
3. TECHNICAL DETAILS
3.1 AFFECTED PRODUCTS
The following versions of Medtronic CareLink and Encore Programmers, devices used by trained personnel at hospitals and clinics to program and manage Medtronic cardiac devices, are affected:
- CareLink 9790 Programmer, all versions,
- CareLink 2090 Programmer, all versions, and
- 29901 Encore Programmer, all versions.
3.2 VULNERABILITY OVERVIEW
The affected products do not encrypt or do not sufficiently encrypt the following sensitive information while at rest:
- PII. Some combination of personal data that enables the unique identification of an individual. PII is defined as “information that can be used to distinguish or trace an individual’s identity, either alone or when combined with other personal or identifying information that is linked or linkable to a specific individual.”
- PHI. Some combination of PII and associated health related data.
- CRITICAL INFRASTRUCTURE SECTORS: Healthcare and Public Health
- COUNTRIES/AREAS DEPLOYED: Worldwide
- COMPANY HEADQUARTERS LOCATION: Ireland
Researchers Billy Rios and Jonathan Butts of Whitescope LLC reported this vulnerability to NCCIC.
The CareLink 9790 Programmer has been placed into end-of-life status and is no longer supported by Medtronic. Medtronic recommends users no longer use the 9790 for any purpose.
The CareLink 2090 and 29901 Encore programmers store PHI and PII as part of their normal operating procedure. Medtronic recommends that when devices are storing PHI/PII it should be retained on these programmers for the least amount of time necessary, and should be handled, managed and secured in a manner consistent with the applicable laws for patient data privacy. Please contact a Medtronic representative for proper disposal and PHI/PII retention setting instructions.
All affected programmers allow for the manual deletion of programmer-generated reports, which could contain PHI/PII. Medtronic recommends users delete these reports when no longer needed and prior to any disposition of the programmer.
Medtronic recommends users take additional defensive measures to minimize the risk of exploitation. Specifically, hospitals and clinicians should:
- Maintain strict physical control of the programmer.
- Use only legitimately obtained programmers and not ones provided by any third party.
Proper disposal of these programmers and the associated electronic media storing data is critical for the continued protection of any PHI and PII residing on the programmer.
Medtronic has released a security bulletin related to this advisory that is available, with contact information, at the following location:
NCCIC reminds organizations to perform proper impact analysis and risk assessment prior to deploying defensive measures.
NCCIC also provides a section for control systems security recommended practices on the ICS-CERT web page. Several recommended practices are available for reading and download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies.
Additional mitigation guidance and recommended practices are publicly available on the ICS-CERT website in the Technical Information Paper, ICS-TIP-12-146-01B--Targeted Cyber Intrusion Detection and Mitigation Strategies.
Organizations observing any suspected malicious activity should follow their established internal procedures and report their findings to NCCIC for tracking and correlation against other incidents.
No known public exploits specifically target this vulnerability. This vulnerability is not exploitable remotely.