Elasticsearch vulnerabilitiesAnd the versions its exploited flaws hit.
Elasticsearch is made by Elastic. We track 42 published vulnerabilities listed under that exact name, across 371 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 25 March 2022. Elastic lists newer releases under their own names, such as Elasticsearch X-Pack, so check those pages too.
The most recent Elasticsearch flaw added to the known-exploited list is CVE-2015-1427, on 25 March 2022. We keep watching the known-exploited list.
Is Elasticsearch listed under other names? Yes.
Elastic also lists Elasticsearch under more specific names, such as Elasticsearch X-Pack. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which versions of Elasticsearch do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "before 1.3.8" means every version up to, but not including, 1.3.8. Find your version, then patch.
- CVE-2015-1427Exploited list, 25 Mar 2022
Elasticsearch Groovy Scripting Engine Remote Code Execution Vulnerability
before 1.3.81.4.0 to before 1.4.3
Which Elasticsearch vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8Elasticsearch Groovy Scripting Engine Remote Code Execution Vulnerability
The Groovy scripting engine in Elasticsearch allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands.
Which Elasticsearch flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%
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.
- 76%CVE-2021-22145Medium
A memory disclosure vulnerability was identified in Elasticsearch 7.10.0 to 7.13.3 error reporting.
- 62%CVE-2023-31419Medium
A flaw was discovered in Elasticsearch, affecting the _search API that allowed a specially crafted query string to cause a Stack Overflow and ultimately a Denial of Service.
- 36%CVE-2021-22146High
All versions of Elastic Cloud Enterprise has the Elasticsearch “anonymous” user enabled by default in deployed clusters.
- 14%CVE-2015-5377Critical
Elasticsearch before 1.6.1 allows remote attackers to execute arbitrary code via unspecified vectors involving the transport protocol.
- 7.5%CVE-2022-23712High
A Denial of Service flaw was discovered in Elasticsearch.
- 2.4%CVE-2021-22144Medium
In Elasticsearch versions before 7.13.3 and 6.8.17 an uncontrolled recursion vulnerability that could lead to a denial of service attack was identified in the Elasticsearch Grok parser.
- 2.4%CVE-2019-7619Medium
Elasticsearch versions 7.0.0-7.3.2 and 6.7.0-6.8.3 contain a username disclosure flaw was found in the API Key service.
- 2.1%CVE-2019-7611High
A permission issue was found in Elasticsearch versions before 5.6.15 and 6.6.1 when Field Level Security and Document Level Security are disabled and the _aliases, _shrink, or _split endpoints are used .
- 2.1%CVE-2023-31418High
An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer.
Running Elasticsearch? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
The Groovy scripting engine in Elasticsearch allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands.
- Matched to
- Elasticsearch on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 42 published vulnerabilities listed under the name Elasticsearch, across 371 versions. The most recent Elasticsearch flaw added to the known-exploited list is CVE-2015-1427, on 25 March 2022.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2015-1427.
Elastic also lists Elasticsearch under more specific names, such as Elasticsearch X-Pack. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Each flaw names its own versions, usually as ranges. The newest, CVE-2015-1427, affects before 1.3.8, 1.4.0 to before 1.4.3. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Elasticsearch. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.