WaratekVRT Sign in

High Elastic CVEs

16 CVEs, 1 exploited, 2 protected by Waratek

Reset
More filters (1)
Columns
Vendor elastic✕
Overview 16 matches · 2 protected · 1 exploited · 1 CISA KEV · 2 public PoC · 2 EPSS ≥ 0.5
16matches 2protected12.5% 1exploited6.2% 1CISA KEV6.2% 2public PoC12.5% 2EPSS ≥ 0.512.5%
Protected by Waratek 2 12.5% Rule in development 0 0.0% Mitigation candidate 1 6.2% No exploit published 13 81.2%
Critical 0 0.0% High 16 100.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 2 12.5% partly blocked 0 0.0% not blocked 14 87.5% not established 0 0.0% unrecorded 0 0.0%
Exploited 1 6.2% Working exploit published 0 0.0% Proof of concept only 1 6.2% Forecast only 0 0.0% No public exploit 14 87.5%
split by peak 5 / year
No exploit published: 13Mitigation candidate: 1Protected by Waratek: 2 High: 16 not blocked: 14blocked by ARMR today: 2 No public exploit: 14Proof of concept only: 1Exploited: 1
20141 Protected by Waratek1 High1 blocked by ARMR today1 Exploited1 20150 20160 20170 20181 No exploit published1 High1 not blocked1 No public exploit1 20190 20202 No exploit published2 High2 not blocked2 No public exploit2 20210 20221 No exploit published1 High1 not blocked1 No public exploit1 20235 Protected by Waratek1 Mitigation candidate1 No exploit published3 High5 blocked by ARMR today1 not blocked4 Proof of concept only1 No public exploit4 20242 No exploit published2 High2 not blocked2 No public exploit2 20254 No exploit published4 High4 not blocked4 No public exploit4
201420152016201720182019202020212022202320242025
16 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2025-37731 High 2025-12-15 No exploit published No public exploit Improper Authentication in Elasticsearch PKI realm can lead to user impersonation via specially crafted client certificates. A malicious actor would need to have such a crafted client certificate signed by a legitimate, trusted Certificate Authority.
CVE-2024-52979 High 2025-05-01 No exploit published No public exploit Uncontrolled Resource Consumption in Elasticsearch while evaluating specifically crafted search templates with Mustache functions can lead to Denial of Service by causing the Elasticsearch node to crash.
CVE-2024-52981 High 2025-04-08 No exploit published No public exploit An issue was discovered in Elasticsearch, where a large recursion using the Well-KnownText formatted string with nested GeometryCollection objects could cause a stackoverflow.
CVE-2024-43709 High 2025-01-21 No exploit published No public exploit An allocation of resources without limits or throttling in Elasticsearch can lead to an OutOfMemoryError exception resulting in a crash via a specially crafted query using an SQL function.
CVE-2024-23444 High 2024-07-31 No exploit published No public exploit It was discovered by Elastic engineering that when elasticsearch-certutil CLI tool is used with the csr option in order to create a new Certificate Signing Requests, the associated private key that is generated is stored on disk unencrypted even if the --pass parameter is passed in the command invocation.
CVE-2024-23450 High 2024-03-27 No exploit published No public exploit A flaw was discovered in Elasticsearch, where processing a document in a deeply nested pipeline on an ingest node could cause the Elasticsearch node to crash.
CVE-2023-46674 High 2023-12-05 Protected by Waratek No public exploit An issue was identified that allowed the unsafe deserialization of java objects from hadoop or spark configuration properties that could have been modified by authenticated users. Elastic would like to thank Yakov Shafranovich, with Amazon Web Services for reporting this issue.
CVE-2023-46673 High 2023-11-22 No exploit published No public exploit It was identified that malformed scripts used in the script processor of an Ingest Pipeline could cause an Elasticsearch node to crash when calling the Simulate Pipeline API.
CVE-2021-37942 High 2023-11-22 No exploit published No public exploit A local privilege escalation issue was found with the APM Java agent, where a user on the system could attach a malicious plugin to an application running the APM Java agent. By using this vulnerability, an attacker could execute code at a potentially higher level of permissions than their user typically has access to.
CVE-2023-31419 High 2023-10-26 Mitigation candidate Proof of concept only 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.
CVE-2023-31418 High 2023-10-26 No exploit published No public exploit An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. An unauthenticated user could force an Elasticsearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests. The issue was identified by Elastic Engineering and we have no indication that the issue is known or that it is being exploited in the wild.
CVE-2022-23712 High 2022-06-06 No exploit published No public exploit A Denial of Service flaw was discovered in Elasticsearch. Using this vulnerability, an unauthenticated attacker could forcibly shut down an Elasticsearch node with a specifically formatted network request.
CVE-2020-7014 High 2020-06-03 No exploit published No public exploit The fix for CVE-2020-7009 was found to be incomplete. Elasticsearch versions from 6.7.0 to 6.8.7 and 7.0.0 to 7.6.1 contain a privilege escalation flaw if an attacker is able to create API keys and also authentication tokens. An attacker who is able to generate an API key and an authentication token can perform a series of steps that result in an authentication token being generated with elevated privileges.
CVE-2020-7009 High 2020-03-31 No exploit published No public exploit Elasticsearch versions from 6.7.0 before 6.8.8 and 7.0.0 before 7.6.2 contain a privilege escalation flaw if an attacker is able to create API keys. An attacker who is able to generate an API key can perform a series of steps that result in an API key being generated with elevated privileges.
CVE-2018-3831 High 2018-09-19 No exploit published No public exploit Elasticsearch Alerting and Monitoring in versions before 6.4.1 or 5.6.12 have an information disclosure issue when secrets are configured via the API. The Elasticsearch _cluster/settings API, when queried, could leak sensitive configuration information such as passwords, tokens, or usernames. This could allow an authenticated Elasticsearch user to improperly view these details.
CVE-2014-3120 High 2014-07-28 Protected by Waratek Exploited The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code via the source parameter to _search. NOTE: this only violates the vendor's intended security policy if the user does not run Elasticsearch in its own independent virtual machine.