WaratekVRT Sign in
Reset
More filters (3)
Columns
ARMR rules: Process✕Published from 2017-09-01✕Published to 2017-09-30✕
Overview 4 matches · 3 protected · 3 exploited · 2 CISA KEV · 3 public PoC · 3 EPSS ≥ 0.5
Protected by Waratek 4 100.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 0 0.0%
Critical 1 25.0% High 3 75.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 3 75.0% partly blocked 1 25.0% not blocked 0 0.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 3 75.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 1 25.0%
split by peak 4 / month
Protected by Waratek: 4 High: 3Critical: 1 partly blocked: 1blocked by ARMR today: 3 No public exploit: 1Exploited: 3
Sep 17
4 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-2017-12611 Critical 2017-09-20 Protected by Waratek Exploited In Apache Struts 2.0.0 through 2.3.33 and 2.5 through 2.5.10.1, using an unintentional expression in a Freemarker tag instead of string literals can lead to a RCE attack.
CVE-2017-12615 High 2017-09-19 Protected by Waratek Exploited When running Apache Tomcat 7.0.0 to 7.0.79 on Windows with HTTP PUTs enabled (e.g. via setting the readonly initialisation parameter of the Default to false) it was possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server.
CVE-2017-9805 High 2017-09-15 Protected by Waratek Exploited The REST Plugin in Apache Struts 2.1.1 through 2.3.x before 2.3.34 and 2.5.x before 2.5.13 uses an XStreamHandler with an instance of XStream for deserialization without any type filtering, which can lead to Remote Code Execution when deserializing XML payloads.
CVE-2017-12612 High 2017-09-13 Protected by Waratek No public exploit In Apache Spark 1.6.0 until 2.1.1, the launcher API performs unsafe deserialization of data received by its socket. This makes applications launched programmatically using the launcher API potentially vulnerable to arbitrary code execution by an attacker with access to any user account on the local machine. It does not affect apps run by spark-submit or spark-shell. The attacker would be able to execute code as the user that ran the Spark application. Users are encouraged to update to version 2.2.0 or later.