ZeroHour
Help Net Securitypublished ()ingested @zeljkazorz

Cryptojacking of businesses' cloud resources still going strong

highRansomwareimportance 60CVE-2014-3120

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2014-3120
Remote Code Execution via Dynamic Scripting in Elasticsearch (CVE-2014-3120)

CVE-2014-3120 is a remote code execution flaw in Elasticsearch that arises when dynamic scripting is enabled, allowing remote attackers to submit arbitrary MVEL expressions and Java code that the cluster evaluates. It is triggered by sending crafted requests to the Elasticsearch API of a cluster where dynamic scripts are permitted, which is the default configuration in legacy releases. An attacker gains arbitrary Java code execution on the server, which public reporting shows being used for cryptojacking, DDoS botnets, and worm-like propagation. Any Elastic Elasticsearch deployment with dynamic scripting enabled is affected. The flaw is listed in CISA KEV (added 2022-03-25), carries an 88.6% EPSS score, and recent honeypot and botnet reporting indicates multiple threat actors are actively exploiting exposed Elasticsearch clusters.

Do: Apply updates per vendor instructions (the CISA KEV required action); current Elasticsearch releases no longer enable dynamic scripting by default, so upgrading removes the exposure. If upgrading is not immediately possible, disable dynamic scripting or restrict script execution, and limit exposure of the Elasticsearch API to trusted networks. Hunt for signs of compromise such as unexpected miner processes, outbound DDoS traffic, or worm-like lateral activity, since Talos honeypot data and WatchDog botnet reporting show this flaw being abused by multiple threat actors.

89% KEV
  • Elasticsearch
large≈ tens of thousands of exposed/legacy Elasticsearch clusters
Full article496 words · extracted from helpnetsecurity.com · click to collapse

In the past year or so, many cybercriminals have turned to cryptojacking as an easier and more low-key approach for “earning” money.

While the value of cryptocurrencies like Bitcoin and Monero has been declining for a while now and Coinhive, the most popular in-browser mining service, has stopped working, cryptojacking is still a considerable threat. After all, attackers need to expand very little effort and are using someone else’s resources for free.

Cybercrooks going after cloud-based assets

Many a security company has noticed the drastic switch from ransomware to cryptojacking – whether performed by stealthily installed malware or in-browser, though scripts – and has warned end users and companies about it.

The latter are especially juicy targets, with a myriad of computing resources (on premises or in the cloud) available for cybercriminals to exploit.

The crooks are using a variety of methods:

  • Getting end users to install malware on their machines (private or corporate) is an easy task, most often achieved by sending an email carrying or pointing to cryptomining malware disguised as something else, or a downloader Trojan that will install a cryptominer at a later date.
  • Compromising websites to serve cryptomining scripts is usually achieved via phishing or brute-forcing of access credentials belonging to web administrators, or by exploiting known vulnerabilities in the underlying software (widely used content management systems such as WordPress or Drupal are the preferred targets). Vulnerable web hosting control panels can also be of use.
  • Compromising container management platforms and cloud environments via misconfigured management interfaces and exposed APIs, misconfigured Kubernetes consoles, or malicious Docker images served via well-established online registries.
  • Compromising servers via vulnerable PHP frameworks and webservers through brute-force attacks.

Latest target: Elasticsearch servers

Threat researchers from F5 Networks have also recently spotted attackers going after Elasticsearch systems.

“The campaign exploits a five-year-old vulnerability (CVE-2014-3120) in Elasticsearch systems running on both Windows and Linux platforms to mine XMR cryptocurrency,” they shared.

The attackers leverage a new method for killing other competing crypto-miners that may already be present on the machines: they redirect their outgoing pool traffic to localhost (“127.0.0.1”).

“In doing so, the competitors’ miners are not able to connect to those cryptocurrency pools and fail to start the mining process, which frees up system resources on the infected machine.” they explained.

The attackers are backdooring the servers to make sure they can access them whenever they want, and are also making sure they will survive a malware cleanup by renaming the original Linux rm (“remove”) command and replacing the binary with a malicious file named rmm that is downloaded from its C&C server.

“The irony is that even if the infected server’s administrator were to detect the other malicious files and try to remove them, she would probably use the rm command which, in turn, would reinstall the malware. Randomly executing the malicious code could make the administrator go crazy trying to understand how the machine continues to get re-infected,” they noted.

Text extracted automatically; images, tables and formatting may be missing. Original: https://www.helpnetsecurity.com/2019/03/18/cryptojacking-cloud-resources/