WaratekVRT Sign in
Reset
More filters (3)
Columns
Published from 2020-08-01✕Published to 2020-08-31✕Vendor opensuse✕
Overview 3 matches · 0 protected · 1 exploited · 0 CISA KEV · 1 public PoC
3matches 0protected0.0% 1exploited33.3% 0CISA KEV0.0% 1public PoC33.3%
Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 1 33.3% No exploit published 2 66.7%
Critical 1 33.3% High 2 66.7% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 3 100.0% 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 3 / month
No exploit published: 2Mitigation candidate: 1 High: 2Critical: 1 not blocked: 3 Forecast only: 2Exploited: 1
Aug 20
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-2020-9490 High 2020-08-07 No exploit published Forecast only Apache HTTP Server versions 2.4.20 to 2.4.43. A specially crafted value for the 'Cache-Digest' header in a HTTP/2 request would result in a crash when the server actually tries to HTTP/2 PUSH a resource afterwards. Configuring the HTTP/2 feature via "H2Push off" will mitigate this vulnerability for unpatched servers.
CVE-2020-11993 High 2020-08-07 No exploit published Forecast only Apache HTTP Server versions 2.4.20 to 2.4.43 When trace/debug was enabled for the HTTP/2 module and on certain traffic edge patterns, logging statements were made on the wrong connection, causing concurrent use of memory pools. Configuring the LogLevel of mod_http2 above "info" will mitigate this vulnerability for unpatched servers.
CVE-2020-11984 Critical 2020-08-07 Mitigation candidate Exploited Apache HTTP server 2.4.32 to 2.4.44 mod_proxy_uwsgi info disclosure and possible RCE