WaratekVRT Sign in
Reset
More filters (2)
Columns
Published to 2025-07-31✕Product http✕
Overview 118 matches · 11 protected · 6 exploited · 2 CISA KEV · 12 public PoC · 13 EPSS ≥ 0.5
split by peak 19 / year
No exploit published: 97Mitigation candidate: 10Protected by Waratek: 11 Low: 4Medium: 54High: 45Critical: 15 not established: 1not blocked: 106blocked by ARMR today: 11 No public exploit: 91Forecast only: 6Proof of concept only: 10Working exploit published: 5Exploited: 6
20011 Mitigation candidate1 Medium1 not blocked1 Working exploit published1 20021 Mitigation candidate1 High1 not blocked1 Working exploit published1 20030 20042 No exploit published2 Medium1 Low1 not blocked2 No public exploit2 20050 20061 No exploit published1 High1 not blocked1 No public exploit1 20073 Protected by Waratek1 No exploit published2 High1 Medium2 blocked by ARMR today1 not blocked2 Working exploit published1 No public exploit2 20080 20091 Mitigation candidate1 Critical1 not blocked1 Exploited1 20100 20111 No exploit published1 Medium1 not blocked1 No public exploit1 20123 Protected by Waratek1 No exploit published2 High1 Medium2 blocked by ARMR today1 not blocked2 No public exploit3 20132 No exploit published2 Medium2 not blocked2 Forecast only1 No public exploit1 20142 Protected by Waratek2 Medium2 blocked by ARMR today2 No public exploit2 20154 No exploit published4 Medium3 Low1 not blocked4 Forecast only1 No public exploit3 20161 No exploit published1 High1 not blocked1 No public exploit1 20174 Mitigation candidate1 No exploit published3 Critical1 High2 Medium1 not blocked4 Proof of concept only1 No public exploit3 20184 No exploit published4 High2 Medium2 not blocked4 No public exploit4 20199 Protected by Waratek1 Mitigation candidate3 No exploit published5 Critical1 High3 Medium5 blocked by ARMR today1 not blocked7 not established1 Exploited2 Working exploit published1 No public exploit6 202018 Protected by Waratek2 Mitigation candidate1 No exploit published15 Critical4 High7 Medium7 blocked by ARMR today2 not blocked16 Exploited2 Forecast only4 No public exploit12 202116 Protected by Waratek3 Mitigation candidate1 No exploit published12 Critical1 High6 Medium8 Low1 blocked by ARMR today3 not blocked13 Working exploit published1 No public exploit15 202219 No exploit published19 Critical4 High7 Medium7 Low1 not blocked19 Proof of concept only2 No public exploit17 20239 Mitigation candidate1 No exploit published8 High5 Medium4 not blocked9 Exploited1 Proof of concept only2 No public exploit6 202413 Protected by Waratek1 No exploit published12 Critical3 High6 Medium4 blocked by ARMR today1 not blocked12 Proof of concept only5 No public exploit8 20254 No exploit published4 High2 Medium2 not blocked4 No public exploit4
2001200320052007200920112013201520172019202120232025
118 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-2015-2808 Low 2015-04-01 No exploit published Forecast only The RC4 algorithm, as used in the TLS protocol and SSL protocol, does not properly combine state data with key data during the initialization phase, which makes it easier for remote attackers to conduct plaintext-recovery attacks against the initial bytes of a stream by sniffing network traffic that occasionally relies on keys affected by the Invariance Weakness, and then using a brute-force approach involving LSB values, aka the "Bar Mitzvah" issue.
CVE-2012-6153 Medium 2014-09-04 Protected by Waratek No public exploit http/conn/ssl/AbstractVerifier.java in Apache Commons HttpClient before 4.2.3 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-5783.
CVE-2014-3577 Medium 2014-08-21 Protected by Waratek No public exploit org.apache.http.conn.ssl.AbstractVerifier in Apache HttpComponents HttpClient before 4.3.5 and HttpAsyncClient before 4.0.2 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 "CN=" string in a field in the distinguished name (DN) of a certificate, as demonstrated by the "foo,CN=www.apache.org" string in the O field.
CVE-2012-5575 Medium 2013-08-19 No exploit published No public exploit Apache CXF 2.5.x before 2.5.10, 2.6.x before CXF 2.6.7, and 2.7.x before CXF 2.7.4 does not verify that a specified cryptographic algorithm is allowed by the WS-SecurityPolicy AlgorithmSuite definition before decrypting, which allows remote attackers to force CXF to use weaker cryptographic algorithms than intended and makes it easier to decrypt communications, aka "XML Encryption backwards compatibility attack."
CVE-2013-2566 Medium 2013-03-15 No exploit published Forecast only The RC4 algorithm, as used in the TLS protocol and SSL protocol, has many single-byte biases, which makes it easier for remote attackers to conduct plaintext-recovery attacks via statistical analysis of ciphertext in a large number of sessions that use the same plaintext.
CVE-2012-5955 High 2012-12-20 No exploit published No public exploit Unspecified vulnerability in the IBM HTTP Server component 5.3 in IBM WebSphere Application Server (WAS) for z/OS allows remote attackers to execute arbitrary commands via unknown vectors.
CVE-2012-5785 Medium 2012-11-04 No exploit published No public exploit Apache Axis2/Java 1.6.2 and earlier does 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-2012-5783 Medium 2012-11-04 Protected by Waratek No public exploit Apache Commons HttpClient 3.x, as used in Amazon Flexible Payments Service (FPS) merchant Java SDK and other products, does 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-2011-1498 Medium 2011-07-07 No exploit published No public exploit Apache HttpClient 4.x before 4.1.1 in Apache HttpComponents, when used with an authenticating proxy server, sends the Proxy-Authorization header to the origin server, which allows remote web servers to obtain sensitive information by logging this header.
CVE-2009-3555 Critical 2009-11-09 Mitigation candidate Exploited The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft Internet Information Services (IIS) 7.0, mod_ssl in the Apache HTTP Server 2.2.14 and earlier, OpenSSL before 0.9.8l, GnuTLS 2.8.5 and earlier, Mozilla Network Security Services (NSS) 3.12.4 and earlier, multiple Cisco products, and other products, does not properly associate renegotiation handshakes with an existing connection, which allows man-in-the-middle attackers to insert data into HTTPS sessions, and possibly other types of sessions protected by TLS or SSL, by sending an unauthenticated request that is processed retroactively by a server in a post-renegotiation context, related to a "plaintext injection" attack, aka the "Project Mogul" issue.
CVE-2007-0450 Medium 2007-03-16 Protected by Waratek Working exploit published Directory traversal vulnerability in Apache HTTP Server and Tomcat 5.x before 5.5.22 and 6.x before 6.0.10, when using certain proxy modules (mod_proxy, mod_rewrite, mod_jk), allows remote attackers to read arbitrary files via a .. (dot dot) sequence with combinations of (1) "/" (slash), (2) "\" (backslash), and (3) URL-encoded backslash (%5C) characters in the URL, which are valid separators in Tomcat but not in Apache.
CVE-2006-6969 Medium 2007-02-07 No exploit published No public exploit Jetty before 4.2.27, 5.1 before 5.1.12, 6.0 before 6.0.2, and 6.1 before 6.1.0pre3 generates predictable session identifiers using java.util.random, which makes it easier for remote attackers to guess a session identifier through brute force attacks, bypass authentication requirements, and possibly conduct cross-site request forgery attacks.
CVE-2007-0279 High 2007-01-17 No exploit published No public exploit Multiple unspecified vulnerabilities in Oracle HTTP Server 9.2.0.8 and Oracle E-Business Suite and Applications 11.5.10CU2 have unknown impact and attack vectors, aka (1) OHS01, (2) OHS02, (3) OHS05, (4) OHS06, and (5) OHS07.
CVE-2006-5350 High 2006-10-18 No exploit published No public exploit Unspecified vulnerability in Oracle HTTP Server 9.2.0.7 and Oracle E-Business Suite and Applications 11.5.10CU2 has unknown impact and local attack vectors, aka Vuln# OHS08.
CVE-2004-2381 Medium 2004-12-31 No exploit published No public exploit HttpRequest.java in Jetty HTTP Server before 4.2.19 allows remote attackers to cause denial of service (memory usage and application crash) via HTTP requests with a large Content-Length.
CVE-2004-1877 Low 2004-03-30 No exploit published No public exploit The p_submit_url value in the sample login form in the Oracle 9i Application Server (9iAS) Single Sign-on Administrators Guide, Release 2(9.0.2) for Oracle SSO allows remote attackers to spoof the login page, which could allow users to inadvertently reveal their username and password.
CVE-2002-2272 High 2002-12-31 Mitigation candidate Working exploit published Tomcat 4.0 through 4.1.12, using mod_jk 1.2.1 module on Apache 1.3 through 1.3.27, allows remote attackers to cause a denial of service (desynchronized communications) via an HTTP GET request with a Transfer-Encoding chunked field with invalid values.
CVE-2001-0122 Medium 2001-03-13 Mitigation candidate Working exploit published Kernel leak in AfpaCache module of the Fast Response Cache Accelerator (FRCA) component of IBM HTTP Server 1.3.x and Websphere 3.52 allows remote attackers to cause a denial of service via a series of malformed HTTP requests that generate a "bad request" error.
‹ prev page 2 of 2 next ›