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.

Cloud

6/8/2016
11:00 AM
Vadim Kotov
Vadim Kotov
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Deconstructing The Impact Of Ransomware On Healthcares IoT

If ransomware targets medical devices, exactly how will an attacker deliver the ransom note to the victim?

Over the past two years, ransomware has spiked in popularity -- both by attackers and in media headlines. This is due in large part to attacks on the general public, who in turn had to fork over cash to regain access when attackers locked down their computers.

With victims increasingly agreeing to pay the ransom, these attacks have evolved into a lucrative business, where cybercriminals are now targeting organizations, large and small, from police departments and banks, to hospitals that store our vital medical data. And ransoms are higher than ever before, with one campaign, CryptoWall 3, having extorted an estimated $325 million.

The issue has become so elevated that the Institute for Critical Infrastructure Technology (ICIT) recently released a report covering the current state of ransomware and threats it may pose in the future. The report suggests that the next inevitable target for ransomware is the Internet of Things (IoT), most notably medical devices.

That poses a very vital question: Is an attacker really primed to hold our pacemakers (or any other critical medical devices for that matter) for ransom?

Graham Cluley, commenting on the ESET blog, claims the threat is not far-fetched, but brings up an interesting question: If ransomware targets medical devices, exactly how will an attacker deliver the ransom note to the victim?

Indeed, laptops, tablets, phones, and other devices have screens, but pacemakers don’t, meaning this kind of attack will require multiple stages. A “smart” pacemaker will probably be controlled by a computer or phone, so the attacker will need to go through these steps: first, hit a device with a display screen; second, perform additional reconnaissance and determine whether it has any IoT devices connected to it; third, lock the IoT devices found; and then finally, pop a ransom note to the user of that computer or phone.

That said, some IoT devices are equipped with an LCD display. Modern cars, for example, have a computer onboard that controls a good deal of the components of the vehicle. Last year security researchers Charlie Miller and Chris Valasek showed how to pretty much take full control of a Jeep Cherokee and also demonstrated that numerous other cars are vulnerable to the same attack. If ransomware took control of the car, it could display the ransom message on the LCD screen or even use the voice generator of the car’s entertainment system. This, however, was a very complex multi-stage exploit that took three years of research.

Pacemaker or PC: Which is really at risk?

For ransomware targeting medical devices, it’s unclear how viable the scenario really is. While it’s likely some criminals will eventually try to infect IoT devices with ransomware, it’s debatable whether it will really take off and reach the scale of current PC ransomware, which is not even as prevalent as other types of malware, according to Microsoft. This contradicts the opening statement of the ICIT report, which says, “2016 is the year ransomware will wreak havoc on America’s critical infrastructure community.” Wreak havoc it will, but if Microsoft’s research is correct -- on a smaller scale than other malware.

We’re now at a point where ransomware has not even conquered the PC world, but it’s already bringing enormous profits to its authors. Does this mean that the underground economy is in balance and we should not expect it to shift significantly to hit IoT, particularly pacemakers, anytime soon?

To answer that, you have to look at the question from the attacker’s perspective. Millions of people use Windows, Internet Explorer, Adobe Flash, etc. Writing one good exploit for, say, Internet Explorer 11 on Windows 7, pretty much guarantees thousands of infections and good profits. Why then would attackers go outside their comfort zone and try to target IoT devices which are far less prevalent than Windows computers and currently have no evident market leader?

They probably wouldn’t if they want to expend the least amount of effort for the maximum results, which is how most financially motivated attackers operate. Besides, although many IoT devices lack security, executing mass attacks with reliable monetization schemes is a challenge.

Targeted attacks are a different story; the more an attacker wants to reach a target, the harder he or she will work to get at the target. Right now, ransomware attacks are targeted at victims that attackers expect will pay, but the victims are easy to reach and if the attack fails, the attackers move on to the next easy target.

With ransomware hitting so many companies and increasingly important targets, like hospitals, I can't help but wonder if IoT devices will be the next targets. I don't think that's going to come anytime soon. That said, there are other dangers lurking for the IoT because device makers aren't building security into the devices and internet connectivity is occurring faster than device manufacturers can keep up with the security implications from software bugs and misconfigurations.

Researchers have shown that a host of connected medical devices can be hacked, from pacemakers to insulin pumps. It's one thing to hold data for ransom; it's another to remotely attack a life-saving device. Either way, it's time to pay closer attention to the security of all connected devices.

Related Content:

 

Vadim Kotov is a security researcher working with Bromium Labs. He has extensive experience in areas of reverse engineering, malware analysis and machine learning. He has presented and/or published research at USENIX CSET, Virus Bulletin and DerbyCon. He also is an active ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
97% of Americans Can't Ace a Basic Security Test
Steve Zurier, Contributing Writer,  5/20/2019
TeamViewer Admits Breach from 2016
Dark Reading Staff 5/20/2019
How a Manufacturing Firm Recovered from a Devastating Ransomware Attack
Kelly Jackson Higgins, Executive Editor at Dark Reading,  5/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5798
PUBLISHED: 2019-05-23
Lack of correct bounds checking in Skia in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.
CVE-2019-5799
PUBLISHED: 2019-05-23
Incorrect inheritance of a new document's policy in Content Security Policy in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to bypass content security policy via a crafted HTML page.
CVE-2019-5800
PUBLISHED: 2019-05-23
Insufficient policy enforcement in Blink in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to bypass content security policy via a crafted HTML page.
CVE-2019-5801
PUBLISHED: 2019-05-23
Incorrect eliding of URLs in Omnibox in Google Chrome on iOS prior to 73.0.3683.75 allowed a remote attacker to perform domain spoofing via a crafted HTML page.
CVE-2019-5802
PUBLISHED: 2019-05-23
Incorrect handling of download origins in Navigation in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to perform domain spoofing via a crafted HTML page.