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.

Application Security //

Ransomware

1/22/2018
09:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

SamSam Ransomware Continues Making Hospitals Sick

SamSam or Samas continues to surface in hospitals and other healthcare facilities. The way the ransomware works shows how vulnerable healthcare is to these particular types of attacks.

SamSam, which also goes by the name Samas, has been an active bugger so far this year. The ransomware has been found at two Indiana hospitals -- one in Greenfield and another in Decatur.

Emphasizing how the threat actors are targeting healthcare in their focused attacks, the ransomware was also found to be present at a cloud-based electronic health records provider.

SamSam has been active since early 2016, when it used vulnerable JBoss application servers to gain a network foothold. Even then, the ransomware was not some widespread attack, but was singularly focused on healthcare targets.

From the beginning, the malware was never dependent on establishing communication with a command and control server, which is how most ransomware operates. It was self-sufficient in operation. It has also always demanded payment in Bitcoin.

By using vulnerable and accessible servers for its entry targets, it bypasses the need for enabling human action or any social engineering. The criminals in this effort have historically first surveyed the infiltrated network before unleashing their encryption, looking for the most valuable files that they can corrupt. This would increase their chances of having a bigger monetary payout when the malware is finally executed.

The current attacks use open Remote Desktop Protocol (RDP) connections to provide an entry point. While their usual technique is to force their way into an RDP connection with a brute-force dictionary attack, it has been reported that the criminals entered one hospital system by using an outside vendor's username and password.

How they obtained these legitimate credentials is unclear.

The affected hospital chose to pay the ransom, even though it had backups available. It seems to have been a business decision at its core, since doing the restore from backups would have cost more than the ransom.

Luckily for the hospital, the threat actors did send a decryption key that unlocked the encrypted records. Most authorities will advise not to pay a ransom in this situation, since a decrypting key may not be returned to the victim.

While SamSam is the symptom, the open RDP on the Internet is the root cause of the infection.

Each of these RDP endpoints has to be extremely validated from a necessary use standpoint before it gets deployed. It goes without saying that a strong password and two-factor authentication should be used on these kinds of connections, but the hospital attack showed that even valid credentials can provide an entry method.

The time has come for the healthcare sector to be cognizant of just how large a target that they are to these criminals. Perhaps then security will rise to the forefront of their operations before some patient's health is compromised.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...