WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕CWE CWE-297✕
Overview 109 matches · 27 in Waratek scope · 1 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
109matches 27in Waratek scope24.8% 1protected0.9% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0% 0EPSS ≥ 0.50.0%
Protected by Waratek 1 0.9% Rule in development 0 0.0% Mitigation candidate 1 0.9% No exploit published 25 22.9% Outside Waratek scope 1 0.9% Not applicable 80 73.4% Withdrawn CVE 1 0.9%
Critical 15 13.8% High 45 41.3% Medium 45 41.3% Low 2 1.8% None 0 0.0% Unknown 2 1.8%
blocked by ARMR today 1 0.9% partly blocked 0 0.0% not blocked 108 99.1% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 0 0.0% Proof of concept only 11 10.1% Forecast only 0 0.0% No public exploit 98 89.9%
split by peak 59 / year
Withdrawn CVE: 1Not applicable: 80Outside Waratek scope: 1No exploit published: 25Mitigation candidate: 1Protected by Waratek: 1 Unknown: 2Low: 2Medium: 45High: 45Critical: 15 not blocked: 108blocked by ARMR today: 1 No public exploit: 98Proof of concept only: 11
20143 No exploit published2 Not applicable1 Medium3 not blocked3 No public exploit3 20150 20161 Not applicable1 Medium1 not blocked1 No public exploit1 20172 Not applicable2 Medium2 not blocked2 No public exploit2 20181 Outside Waratek scope1 High1 not blocked1 No public exploit1 20191 No exploit published1 Medium1 not blocked1 No public exploit1 20205 No exploit published3 Not applicable2 Critical2 Medium3 not blocked5 No public exploit5 20215 No exploit published1 Not applicable4 Critical1 High3 Medium1 not blocked5 No public exploit5 20224 No exploit published2 Not applicable2 High3 Medium1 not blocked4 No public exploit4 20238 Not applicable8 High3 Medium5 not blocked8 No public exploit8 20248 No exploit published2 Not applicable6 High4 Medium4 not blocked8 Proof of concept only1 No public exploit7 202512 No exploit published3 Not applicable9 Critical1 High5 Medium6 not blocked12 Proof of concept only2 No public exploit10 202659 Protected by Waratek1 Mitigation candidate1 No exploit published11 Not applicable45 Withdrawn CVE1 Critical11 High26 Medium18 Low2 Unknown2 blocked by ARMR today1 not blocked58 Proof of concept only8 No public exploit51
2014201620182020202220242026
109 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed. ‹ prev page 2 of 2 next ›
CVE Severity Published▾ Status Exploitation Description
CVE-2020-1887 Critical 2020-03-13 Not applicable No public exploit Incorrect validation of the TLS SNI hostname in osquery versions after 2.9.0 and before 4.2.0 could allow an attacker to MITM osquery traffic in the absence of a configured root chain of trust.
CVE-2014-3603 Medium 2019-04-04 No exploit published No public exploit The (1) HttpResource and (2) FileBackedHttpResource implementations in Shibboleth Identity Provider (IdP) before 2.4.1 and OpenSAML Java 2.6.2 do not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.
CVE-2018-10936 High 2018-08-30 Outside Waratek scope No public exploit A weakness was found in postgresql-jdbc before version 42.2.5. It was possible to provide an SSL Factory and not check the host name if a host name verifier was not provided to the driver. This could lead to a condition where a man-in-the-middle attacker could masquerade as a trusted server by providing a certificate for the wrong host, as long as it was signed by a trusted CA.
CVE-2017-2912 Medium 2017-11-07 Not applicable No public exploit An exploitable vulnerability exists in the remote control functionality of Circle with Disney running firmware 2.0.1. SSL certificates for specific domain names can cause the goclient daemon to accept a different certificate than intended. An attacker can host an HTTPS server with this certificate to trigger this vulnerability.
CVE-2017-2911 Medium 2017-11-07 Not applicable No public exploit An exploitable vulnerability exists in the remote control functionality of Circle with Disney running firmware 2.0.1. SSL certificates for specific domain names can cause the rclient daemon to accept a different certificate than intended. An attacker can host an HTTPS server with this certificate to trigger this vulnerability.
CVE-2016-1280 Medium 2016-09-09 Not applicable No public exploit PKId in Juniper Junos OS before 12.1X44-D52, 12.1X46 before 12.1X46-D37, 12.1X47 before 12.1X47-D30, 12.3 before 12.3R12, 12.3X48 before 12.3X48-D20, 13.3 before 13.3R10, 14.1 before 14.1R8, 14.1X53 before 14.1X53-D40, 14.2 before 14.2R7, 15.1 before 15.1R4, 15.1X49 before 15.1X49-D20, 15.1X53 before 15.1X53-D60, and 16.1 before 16.1R1 allow remote attackers to bypass an intended certificate validation mechanism via a self-signed certificate with an Issuer name that matches a valid CA certificate enrolled in Junos.
CVE-2014-3604 Medium 2014-10-25 No exploit published No public exploit Certificates.java in Not Yet Commons SSL before 0.3.15 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.
CVE-2014-3596 Medium 2014-08-27 No exploit published No public exploit The getCN function in Apache Axis 1.4 and earlier does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a certificate with a subject that specifies a common name in a field that is not the CN field. NOTE: this issue exists because of an incomplete fix for CVE-2012-5784.
CVE-2014-3522 Medium 2014-08-19 Not applicable No public exploit The Serf RA layer in Apache Subversion 1.4.0 through 1.7.x before 1.7.18 and 1.8.x before 1.8.10 does not properly handle wildcards in the Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof servers via a crafted certificate.
‹ prev page 2 of 2 next ›