Elasticsearch CVEs · Protected by Waratek · High

VRT Sign in

Look up CVE IDs Status Exploitation Severity

Reset

Overview 2 matches · 1 exploited · 1 CISA KEV · 1 public PoC · 1 EPSS ≥ 0.5

2matches 1exploited50.0% 1CISA KEV50.0% 1public PoC50.0% 1EPSS ≥ 0.550.0%

Protected by Waratek 2 100.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 0 0.0%

Critical 0 0.0% High 2 100.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%

blocked by ARMR today 2 100.0% partly blocked 0 0.0% not blocked 0 0.0% not established 0 0.0% unrecorded 0 0.0%

Exploited 1 50.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 1 50.0%

split by StatusSeverityProtectionExploit maturity peak 1 / year

20141 Protected by Waratek1 High1 blocked by ARMR today1 Exploited1 20150 20160 20170 20180 20190 20200 20210 20220 20231 Protected by Waratek1 High1 blocked by ARMR today1 No public exploit1

2014201520162017201820192020202120222023

2 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-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-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.

CVE

Severity

Published▾

Status

Exploitation

Description

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-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.