WaratekVRT Sign in
Reset
More filters (2)
Columns
Including CVEs outside Waratek scope✕Product oncommand system manager✕Has a public PoC✕
Overview 9 matches · 5 in Waratek scope · 3 protected · 4 exploited · 2 CISA KEV · 6 EPSS ≥ 0.5
9matches 5in Waratek scope55.6% 3protected33.3% 4exploited44.4% 2CISA KEV22.2% 6EPSS ≥ 0.566.7%
Protected by Waratek 3 33.3% Rule in development 0 0.0% Mitigation candidate 2 22.2% No exploit published 0 0.0% Outside Waratek scope 4 44.4% Not applicable 0 0.0% Withdrawn CVE 0 0.0%
Critical 2 22.2% High 2 22.2% Medium 5 55.6% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 3 33.3% partly blocked 0 0.0% not blocked 6 66.7% not established 0 0.0% unrecorded 0 0.0%
Exploited 4 44.4% Working exploit published 3 33.3% Proof of concept only 2 22.2% Forecast only 0 0.0% No public exploit 0 0.0%
split by peak 2 / month
Outside Waratek scope: 4Mitigation candidate: 2Protected by Waratek: 3 Medium: 5High: 2Critical: 2 not blocked: 6blocked by ARMR today: 3 Proof of concept only: 2Working exploit published: 3Exploited: 4
Apr 191 Outside Waratek scope1 Medium1 not blocked1 Exploited1 May 190 Jun 190 Jul 190 Aug 190 Sep 190 Oct 190 Nov 190 Dec 191 Protected by Waratek1 Critical1 blocked by ARMR today1 Proof of concept only1 Jan 201 Outside Waratek scope1 Medium1 not blocked1 Working exploit published1 Feb 201 Protected by Waratek1 Critical1 blocked by ARMR today1 Exploited1 Mar 200 Apr 202 Outside Waratek scope2 Medium2 not blocked2 Exploited2 May 201 Protected by Waratek1 Medium1 blocked by ARMR today1 Working exploit published1 Jun 201 Mitigation candidate1 High1 not blocked1 Proof of concept only1 Jul 201 Mitigation candidate1 High1 not blocked1 Working exploit published1
May 19Jul 19Sep 19Nov 19Jan 20Mar 20May 20Jul 20
9 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-2020-13935 High 2020-07-14 Mitigation candidate Working exploit published The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56 and 7.0.27 to 7.0.104. Invalid payload lengths could trigger an infinite loop. Multiple requests with invalid payload lengths could lead to a denial of service.
CVE-2020-11996 High 2020-06-26 Mitigation candidate Proof of concept only A specially crafted sequence of HTTP/2 requests sent to Apache Tomcat 10.0.0-M1 to 10.0.0-M5, 9.0.0.M1 to 9.0.35 and 8.5.0 to 8.5.55 could trigger high CPU usage for several seconds. If a sufficient number of such requests were made on concurrent HTTP/2 connections, the server could become unresponsive.
CVE-2020-7656 Medium 2020-05-19 Protected by Waratek Working exploit published jquery prior to 1.9.0 allows Cross-site Scripting attacks via the load method. The load method fails to recognize and remove "<script>" HTML tags that contain a whitespace character, i.e: "</script >", which results in the enclosed script logic to be executed.
CVE-2020-11023 Medium 2020-04-29 Outside Waratek scope Exploited In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2020-11022 Medium 2020-04-29 Outside Waratek scope Exploited In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2020-1938 Critical 2020-02-24 Protected by Waratek Exploited When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited in ways that may be surprising. In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. This vulnerability report identified a mechanism that allowed: - returning arbitrary files from anywhere in the web application - processing any file in the web application as a JSP Further, if the web application allowed file upload and stored those files within the web application (or the attacker was able to control the content of the web application by some other means) then this, along with the ability to process a file as a JSP, made remote code execution possible. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users. Users wishing to take a defence-in-depth approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. It is likely that users upgrading to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations.
CVE-2013-3320 Medium 2020-01-29 Outside Waratek scope Working exploit published Cross-site Scripting (XSS) vulnerability in NetApp OnCommand System Manager before 2.2 allows remote attackers to inject arbitrary web script or HTML via the 'full-name' and 'comment' fields.
CVE-2019-17571 Critical 2019-12-20 Protected by Waratek Proof of concept only Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
CVE-2019-11358 Medium 2019-04-20 Outside Waratek scope Exploited jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.