WaratekVRT Sign in
Reset
More filters (2)
Columns
EPSS ≥ 0.5✕Oracle product: Oracle REST Data Services✕
Overview 3 matches · 1 protected · 1 exploited · 0 CISA KEV · 1 public PoC
3matches 1protected33.3% 1exploited33.3% 0CISA KEV0.0% 1public PoC33.3%
Protected by Waratek 1 33.3% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 2 66.7%
Critical 0 0.0% High 1 33.3% Medium 2 66.7% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 1 33.3% partly blocked 0 0.0% not blocked 2 66.7% not established 0 0.0% unrecorded 0 0.0%
Exploited 1 33.3% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 2 66.7% No public exploit 0 0.0%
split by peak 1 / month
No exploit published: 2Protected by Waratek: 1 Medium: 2High: 1 not blocked: 2blocked by ARMR today: 1 Forecast only: 2Exploited: 1
Feb 211 No exploit published1 Medium1 not blocked1 Forecast only1 Mar 210 Apr 211 No exploit published1 High1 not blocked1 Forecast only1 May 210 Jun 210 Jul 211 Protected by Waratek1 Medium1 blocked by ARMR today1 Exploited1
Feb 21Mar 21Apr 21May 21Jun 21Jul 21
3 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-2021-34429 Medium 2021-07-15 Protected by Waratek Exploited For Eclipse Jetty versions 9.4.37-9.4.42, 10.0.1-10.0.5 & 11.0.1-11.0.5, URIs can be crafted using some encoded characters to access the content of the WEB-INF directory and/or bypass some security constraints. This is a variation of the vulnerability reported in CVE-2021-28164/GHSA-v7ff-8wcx-gmc5.
CVE-2021-28165 High 2021-04-01 No exploit published Forecast only In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.
CVE-2020-27223 Medium 2021-02-26 No exploit published Forecast only In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality” (i.e. q) parameters, the server may enter a denial of service (DoS) state due to high CPU usage processing those quality values, resulting in minutes of CPU time exhausted processing those quality values.