WaratekVRT Sign in
Reset
More filters (3)
Columns
Published from 2019-07-01✕Published to 2019-09-30✕Product element✕
Overview 4 matches · 0 protected · 1 exploited · 0 CISA KEV · 1 public PoC · 2 EPSS ≥ 0.5
Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 2 50.0% No exploit published 2 50.0%
Critical 1 25.0% High 2 50.0% Medium 1 25.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 75.0% not established 1 25.0% unrecorded 0 0.0%
split by peak 3 / month
No exploit published: 2Mitigation candidate: 2 Medium: 1High: 2Critical: 1 not established: 1not blocked: 3 No public exploit: 2Working exploit published: 1Exploited: 1
Aug 19Sep 19
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-2019-10097 High 2019-09-26 Mitigation candidate Exploited In Apache HTTP Server 2.4.32-2.4.39, when mod_remoteip was configured to use a trusted intermediary proxy server using the "PROXY" protocol, a specially crafted PROXY header could trigger a stack buffer overflow or NULL pointer deference. This vulnerability could only be triggered by a trusted proxy and not by untrusted HTTP clients.
CVE-2019-10092 Medium 2019-09-26 Mitigation candidate Working exploit published In Apache HTTP Server 2.4.0-2.4.39, a limited cross-site scripting issue was reported affecting the mod_proxy error page. An attacker could cause the link on the error page to be malformed and instead point to a page of their choice. This would only be exploitable where a server was set up with proxying enabled but was misconfigured in such a way that the Proxy Error page was displayed.
CVE-2019-10082 Critical 2019-09-26 No exploit published No public exploit In Apache HTTP Server 2.4.18-2.4.39, using fuzzed network input, the http/2 session handling could be made to read memory after being freed, during connection shutdown.
CVE-2019-12402 High 2019-08-30 No exploit published No public exploit The file name encoding algorithm used internally in Apache Commons Compress 1.15 to 1.18 can get into an infinite loop when faced with specially crafted inputs. This can lead to a denial of service attack if an attacker can choose the file names inside of an archive created by Compress.