Security leaders in the healthcare industry know the common refrain about medical devices: legacy technology permeates, none of it was meant to be connected to the internet, and all of it is too expensive to replace. Underlying this dynamic is the reality that many medical devices contain serious vulnerabilities, some of which have known exploits in the wild. Replacing devices, meanwhile, hinges on component failures rather than cybersecurity concerns—even though some of these vulnerabilities could lead to negative patient outcomes.
This is the backdrop for Team82’s first healthcare cybersecurity report. Available now, the State of CPS Security Report: Healthcare 2023 puts real numbers behind the vulnerabilities and architectural weaknesses that are not only endangering the availability and reliability of life-saving medical equipment, but also patient safety.
We urge you to download the report and take time to examine our findings; we believe healthcare delivery organizations are at a pivotal point. Security leaders and medical device manufacturers can no longer be reactive about cybersecurity. Patient safety as it relates to cyber must be a core business consideration for HDOs, and security must inform decision-makers, policy-makers, and vendors alike.
Let’s examine some of our key findings:
One important data source for this report was CISA’s Known Exploitable Vulnerabilites (KEV) catalog, a database of vulnerabilities that have been publicly attacked. From our research, we discovered that 63% of KEVs tracked by CISA can be found on healthcare networks, 23% of medical devices (imaging systems, clinical IoT devices, surgical equipment) have at least one KEV, and 14% of electronic health record systems.
We break that down further, below.
Patching vulnerabilities in medical devices is complex; while many medical device manufacturers develop on Windows or Linux, for example, two platforms that are regularly updated, the same capabilities are often not built into medical devices. Patching is often an expensive add-on support contracts, according to HDOs we spoke to. HDOs must often rely on compensate controls to mitigate the exposure and potential impact of these vulnerabilities if they’re exploited. MDMs, for their part, argue that because of the Food and Drug Administration’s lengthy device certification process they are concerned about breaking FDA-certified functionality and maybe be hesitant about investing in complete security testing.
In addition to KEVs, we discovered devices containing vulnerabilities that have a high Exploit Prediction Scoring System (EPSS) score. These scores, as determined by FIRST, estimate the probability of a vulnerability being exploited within 30 days of public disclosure (EPSS scores do not present a complete picture of risk and should be a consideration along with other metrics when prioritizing vulnerability remediation and mitigation options).
We discovered high EPSS scores especially rampant in hospital systems and medical devices running on unsupported operating systems, those considered end-of-life by a MDM and no longer supported with feature or security updates.
We also found relatively high numbers of imaging devices (MRIs, CT scanning machines) to contain vulnerabilities with high EPSS score, and even surgical devices, and other patient support systems.
The proliferation of remotely controleld and monitored medical devices has introduced weaknesses in network architectures that put devices and patienst at risk. For example, our research shows a number of life-saving medical devices—including surgical equipment–accessible from networks labeled “guest networks” by hospitals. A skilled attacker can bridge the two networks and burrow deeper into the internal network.
Our research shows that legacy medical devices running on unsupported and/or unmanaged operating systems are prevalent on hospital networks. These systems are considered end-of-life by their respective vendors and are no longer supplied with security or feature updates. Below are some data points around legacy systems from our research.
CWE-547 USE OF HARD-CODED, SECURITY-RELEVANT CONSTANTS:
Optigo Networks Visual BACnet Capture Tool and Optigo Visual Networks Capture Tool version 3.1.2rc11 are vulnerable to an attacker impersonating the web application service and mislead victim clients.
Optigo Networks recommends users to upgrade to the following:
CVSS v3: 7.5
CWE-288 AUTHENTICATION BYPASS USING AN ALTERNATE PATH OR CHANNEL:
Optigo Networks Visual BACnet Capture Tool and Optigo Visual Networks Capture Tool version 3.1.2rc11 contain an exposed web management service that could allow an attacker to bypass authentication measures and gain controls over utilities within the products.
Optigo Networks recommends users to upgrade to the following:
CVSS v3: 9.8
CWE-547 USE OF HARD-CODED, SECURITY-RELEVANT CONSTANTS:
Optigo Networks Visual BACnet Capture Tool and Optigo Visual Networks Capture Tool version 3.1.2rc11 contain a hard coded secret key. This could allow an attacker to generate valid JWT (JSON Web Token) sessions.
Optigo Networks recommends users to upgrade to the following:
CVSS v3: 7.5
CWE-912 HIDDEN FUNCTIONALITY:
The "update" binary in the firmware of the affected product sends attempts to mount to a hard-coded, routable IP address, bypassing existing device network settings to do so. The function triggers if the 'C' button is pressed at a specific time during the boot process. If an attacker is able to control or impersonate this IP address, they could upload and overwrite files on the device.
Per FDA recommendation, CISA recommends users remove any Contec CMS8000 devices from their networks.
If asset owners cannot remove the devices from their networks, users should block 202.114.4.0/24 from their networks, or block 202.114.4.119 and 202.114.4.120.
Please note that this device may be re-labeled and sold by resellers.
Read more here: Do the CONTEC CMS8000 Patient Monitors Contain a Chinese Backdoor? The Reality is More Complicated….
CVSS v3: 7.5
CWE-295 IMPROPER CERTIFICATE VALIDATION:
The affected product is vulnerable due to failure of the update mechanism to verify the update server's certificate which could allow an attacker to alter network traffic and carry out a machine-in-the-middle attack (MITM). An attacker could modify the server's response and deliver a malicious update to the user.
Medixant recommends users download the v2025.1 or later version of their software.
CVSS v3: 5.7