Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

6/8/2015
04:00 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
100%
0%

Hospital Medical Devices Used As Weapons In Cyberattacks

Security firm discovered malware-infected medical devices in three hospitals hit by data breaches.

Insulin pumps, heart monitors, x-ray communications systems and other medical devices already have been proven vulnerable to cyberattack by security researchers, but a new report confirms that hospital medical devices are being abused by cybercriminals and possibly cyberspies as a stepping-stone within healthcare networks to nab valuable healthcare identities and information.

A report by TrapX scheduled to publish next week reveals three cases where hospitals were hit by data breaches after their medical devices had been infected with malware backdoors to move laterally within the healthcare network. In all three cases, the hospitals were unaware that these devices--a blood gas analyzer, a picture archive and communications system (PACS) and an x-ray system--were infiltrated with malware. The devices were spotted when TrapX installed its sensor-based technology in the hospitals, which TrapX declined to identify by name.

Ransomware, as well as Zeus, Citadel, and even Conficker, malware were discovered on the devices. While none of these real-world hacks of the medical devices appeared to be used for sabotage per se, TrapX says the malware on them indeed could be used for remote control of the devices.  

"We did see multiple types of malware and ransomware resident on these [medical] devices," says Greg Enriquez, CEO of TrapX. The hospital's security teams were unable to see the malware themselves via their traditional security scans and tools because the systems are closed devices, he says.

"They're not open to security teams to scan or to use typical security products on," he says. "That's the challenge hospital professionals have in security: often these devices are behind secondary firewalls managed by the manufacturer of the device, and the security team doesn't have access."

Billy Rios, a security researcher who has studied various types of consumer and medical system vulnerabilities, says malware attacks on medical devices are "pretty common."

Some of these devices are based on Windows, for example, Rios says, so they are often susceptible to Windows exploits. "There have been previously reported cases where these devices have become infected by run-of-the-mill malware.  While this malware isn't custom-made for medical devices, it shows that the devices are vulnerable to exploitation," says Rios, who is founder of Laconicly LLC.

The attacks on the three hospitals were targeted in nature. In one case, three blood-gas analyzers were infected with malware within the hospital, which had in place a firewall, heuristics-based intrusion detection, endpoint security, and antivirus tools, as well as an experienced security team. The hospital had no clue of the infections until TrapX installed its sensors, and noticed several alerts about malicious activity in the hospital network. Each system had a backdoor that gave them access to the internal network, and hospital data records had been exfiltrated to somewhere in the European Community, TrapX says.

Zeus and Citadel Trojans were in place to grab passwords, and a worm was also found to spread and propagate the malware. "The devices had an early version of Windows," Enriquez says, which made them more vulnerable.

In the second case, a hospital's picture archive and communications system (PACS) used to share imaging records from MRI, CT, ultrasound, x-ray systems with physicians and others, was infected with malware.

As with the other hacked hospital, this one also had the proper security tools and staff in place, but had no clue that the PACS had been compromised. In this case, data was being siphoned out and sent to a location in Guiyang, China, via an SSL-encrypted port 443, suggesting a possible cyber espionage attack.

"We clearly saw it going to China," Enriquez says. "Where it goes from there, how it gets routed … that's unknown at this point."

The attack began with a user at the hospital visiting a malicious website that injected a Java exploit into the user's browser and provided remote access to the attackers, and ultimately, the injection of malware backdoor on the PACS, according to TrapX.

[Public safety may finally force Internet of Things manufacturers to start taking security seriously. Read Internet Of Things Security Reaches Tipping Point.]

In the third hospital, one of the x-ray systems was found harboring a backdoor for a "pivot" attack on the hospital network, the company said.

"I believe these medical providers were targeted. They are being targeted for a number of reasons: personal information is worth ten times more on the black market than a credit card number, and the personal information they have may have value to a nation-state," Enriquez says.

TrapX's "Anatomy of an Attack – Medical Device Hijack (MEDJACK)," will be released on June 15. The company says hospitals should include language in their contracts with medical equipment makers that covers malware infections. "They must include very specific language about the detection, remediation and refurbishment of the medical devices sold to the hospitals which are infected by the malware. They must have a documented test process to determine if they are infected, and a documented standard process to remediate and rebuild them when malware and cyber attackers are using the devices," says Mosh Ben Simon, co-founder and vice president of TrapX Security and general manager of TrapX Labs, in the report.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
KennedyAngel
0%
100%
KennedyAngel,
User Rank: Apprentice
7/3/2015 | 8:29:45 AM
Re: Surprised I'm surprised
Computer malware and viruses are rapidly setting their sights on medical devices. Many medical devices like fetal monitors, pacemakers, insulin pump and many more dependent on networks, always have the possibility to face cyber attack. Patients remain at risk, thus to prevent this condition, FDA officials have announced new guidelines to medical device manufacturers like present at ilexmedical.com for outlining the cyber security issues. If the manufacturers don't adequately overcome cyber threat concerns, then devices might be blocked for practical use.
dieselnerd
50%
50%
dieselnerd,
User Rank: Strategist
6/11/2015 | 1:12:38 PM
Re: Surprised I'm surprised
Another wake-up call, another slap to the Snooze button. We are masters of denial - and masters of avoiding investment in maintenance/protection.
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
6/9/2015 | 8:00:28 AM
Re: Surprised I'm surprised
Isolating these systems comes with the same challenges as critical systems in the ICS/SCADA world...even if you think you've air-gapped them (which you can't really do with an x-ray imaging system, anyway, because docs need to access the images), there's always a way to infect them as soon as someone plugs a laptop or tablet in, or even a USB stick. What needs to happen is better built-in security and forensics capabilities, as well as more good 'ol defense-in-depth.
Whoopty
50%
50%
Whoopty,
User Rank: Ninja
6/9/2015 | 7:55:18 AM
Surprised I'm surprised
I'm surprised by this, though considering the security in many other industries, its shouldn't come as such. Still, this should act as a big wake up call as we move towards a future with lots of wearable data being used in the medical fields, that better security is required. 

Keeping all of it on its own network seems like a good place to start. 
US Turning Up the Heat on North Korea's Cyber Threat Operations
Jai Vijayan, Contributing Writer,  9/16/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/2019
NetCAT Vulnerability Is Out of the Bag
Dark Reading Staff 9/12/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16395
PUBLISHED: 2019-09-17
GnuCOBOL 2.2 has a stack-based buffer overflow in the cb_name() function in cobc/tree.c via crafted COBOL source code.
CVE-2019-16396
PUBLISHED: 2019-09-17
GnuCOBOL 2.2 has a use-after-free in the end_scope_of_program_name() function in cobc/parser.y via crafted COBOL source code.
CVE-2019-16199
PUBLISHED: 2019-09-17
eQ-3 Homematic CCU2 before 2.47.18 and CCU3 before 3.47.18 allow Remote Code Execution by unauthenticated attackers with access to the web interface via an HTTP POST request to certain URLs related to the ReGa core process.
CVE-2019-16391
PUBLISHED: 2019-09-17
SPIP before 3.1.11 and 3.2 before 3.2.5 allows authenticated visitors to modify any published content and execute other modifications in the database. This is related to ecrire/inc/meta.php and ecrire/inc/securiser_action.php.
CVE-2019-16392
PUBLISHED: 2019-09-17
SPIP before 3.1.11 and 3.2 before 3.2.5 allows prive/formulaires/login.php XSS via error messages.