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 Security

// // //

AWS Elasticsearch Servers Host Malware

Two strains of POS malware have been using Elasticsearch servers on AWS as hiding places.

Cloud-hosted servers are at the root of yet another malware outbreak as more than 4,000 ElasticSearch servers, most hosted on AWS, have been found to be infected with two strains of malware aimed at point-of-sale (POS) terminals. The malware -- AlinaPOS and JackPOS -- has been around for at least five years but is now being widely sold on dark web malware sites.

Researchers at Kromtech discovered the malware instances during research on Elasticsearch and found that many of the servers had been infected multiple times with multiple versions of the malware. The question is, why were the Elasticsearch instances on AWS hit particularly hard?

Elasticsearch is an open-source search and analytics engine that is fully indexed so searches are very fast. It can run on very small hardware footprints and that's why so many Elasticsearch servers are hosted on AWS -- and why a particular vulnerability to this malware exists. According to the Kromtech research blog post:

Amazon Web Services provides customers with a free T2 micro (EC2 / Elastic Compute Cloud) instance with up to 10 Gb of disk space. These T2 instances are designed for operations that don't use the full CPU for general purpose workloads, such as web servers, developer environments, and small databases. The problem is that on the T2 micro, you can set only versions 1.5.2 and 2.3.2.

Amazon makes it very fast and very easy to set up one of these Elasticsearch instances. Unfortunately, the speed and ease make it very fast and easy to skip all the security settings, leaving both functionality and administration of the Elasticsearch instance open to the world. And everyone knows that there is little that a hacker loves more than an unlocked, open instance.

So what are companies to do with Elasticsearch instances that they now assume to be infected? The Kromtech Security Center has a list of suggestion in the blog post announcing the find; the points of the list boil down to tear down the instance, throw it away and start over from a known-good image.


Get real-world answers to virtualization challenges from industry leaders. Join us for the NFV & Carrier SDN event in Denver. Register now for this exclusive opportunity to learn from and network with industry experts -- communications service providers get in free!

Elastic has their own list of security suggestions which are largely things that should be done as part of all security processes for all applications and infrastructure components. To both of these sets of suggestions, Security Now has one more that seems necessary on the heels of recent vulnerabilities.

Be careful when you configure cloud-based servers. Don't click in rapid-fire fashion through security questions and setup parameters. Take the few minutes required to understand what you're setting up and why. Proper cloud setup isn't necessarily hard: It just takes thought and a little bit of patience. And it could pay off in the joy that comes through knowing that you're not a major stop on the dark web malware repository road.

Related posts:

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Machine Learning, AI & Deep Learning Improve Cybersecurity
Machine intelligence is influencing all aspects of cybersecurity. Organizations are implementing AI-based security to analyze event data using ML models that identify attack patterns and increase automation. Before security teams can take advantage of AI and ML tools, they need to know what is possible. This report covers: -How to assess the vendor's AI/ML claims -Defining success criteria for AI/ML implementations -Challenges when implementing AI
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-42002
PUBLISHED: 2022-10-01
SonicJS through 0.6.0 allows file overwrite. It has the following mutations that are used for updating files: fileCreate and fileUpdate. Both of these mutations can be called without any authentication to overwrite any files on a SonicJS application, leading to Arbitrary File Write and Delete.
CVE-2022-39268
PUBLISHED: 2022-09-30
### Impact In a CSRF attack, an innocent end user is tricked by an attacker into submitting a web request that they did not intend. This may cause actions to be performed on the website that can include inadvertent client or server data leakage, change of session state, or manipulation of an end use...
CVE-2022-34428
PUBLISHED: 2022-09-30
Dell Hybrid Client prior to version 1.8 contains a Regular Expression Denial of Service Vulnerability in the UI. An adversary with WMS group admin access could potentially exploit this vulnerability, leading to temporary denial-of-service.
CVE-2022-34429
PUBLISHED: 2022-09-30
Dell Hybrid Client below 1.8 version contains a Zip Slip Vulnerability in UI. A guest privilege attacker could potentially exploit this vulnerability, leading to system files modification.
CVE-2022-40923
PUBLISHED: 2022-09-30
A vulnerability in the LIEF::MachO::SegmentCommand::virtual_address function of LIEF v0.12.1 allows attackers to cause a denial of service (DOS) through a segmentation fault via a crafted MachO file.