CVE-2015-1427

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Elasticsearch. For every flaw being used in attacks, see Exploited flaws; for Elastic’s, see Elastic flaws being used in attacks.

CVE-2015-1427 is a security flaw in Elasticsearch. Attackers can run their own code on Elasticsearch. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 25 Mar 2022.[1]

Elasticsearch is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Elastic has published a fix or advice.

Description

CISA calls it a groovy scripting engine remote code execution in Elastic Elasticsearch. In its words: “The Groovy scripting engine in Elasticsearch allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands.”[1]

The CVE record adds: “The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands via a crafted script.”[2]

The underlying weakness is improper access control (CWE-284), in MITRE’s list of common software weaknesses.

It scores 9.8 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by NVD using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it; Elastic’s advisory has them[3]. CISA names the product as Elastic Elasticsearch.

Most families won’t have Elasticsearch; it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 25 Mar 2022, 2,593 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 15 Apr 2022 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at over 99%. That’s in the top 1% of the flaws it scores.[4]

CISA assesses it as automatable: attackers can run it against many targets at once.

CISA doesn’t say who was attacked, or how.

Fix

Elastic has published a fix or advice.[3] CISA’s required action: “Apply updates per vendor instructions.”[1]

  1. Check whether you use it.Elasticsearch is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 15 Apr 2022 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 9.8.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at over 99%.[4]

See also

Other Elasticsearch flaws

Other Elastic flaws

  • CVE-2019-7609, Elastic Kibana: arbitrary code execution ·

Other improper access control flaws

  • CVE-2015-3306, ProFTPD: improper access control ·
  • CVE-2026-21962, Oracle HTTP Server and Oracle Weblogic Server Proxy Plug-in: improper access control ·
  • CVE-2026-56290, Joomlack Page Builder: improper access control ·
  • CVE-2026-34908, Ubiquiti UniFi OS: improper access control ·
  • CVE-2026-48907, Widget Factory Joomla Content Editor: improper access control ·

Added the same day

  • CVE-2022-26318, WatchGuard Firebox and XTM Appliances: arbitrary code execution ·
  • CVE-2022-26143, Mitel MiCollab, MiVoice Business Express: access control ·
  • CVE-2022-21999, Microsoft Windows: print spooler privilege escalation ·
  • CVE-2021-42237, Sitecore XP: remote command execution ·
  • CVE-2021-22941, Citrix ShareFile: improper access control ·

Every Elastic flaw on CISA’s list · Everything added in March 2022

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Elasticsearch Groovy Scripting Engine Remote Code Execution Vulnerability”. Known Exploited Vulnerabilities Catalog, added 25 Mar 2022.
  2. ^ National Institute of Standards and Technology. “CVE-2015-1427 Detail”. National Vulnerability Database, published 17 Feb 2015.
  3. ^ Elastic. Advisories and fixes: elastic.co.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.999, percentile 100.0, 31 Oct 2026.
  5. CVE Program. “CVE-2015-1427”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.