CWE-295 CVEs
126 CVEs, 2 protected by Waratek
Overview 126 matches · 2 protected · 0 exploited · 0 CISA KEV · 1 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
2
1.6%
Rule in development
0
0.0%
Mitigation candidate
2
1.6%
No exploit published
122
96.8%
blocked by ARMR today
2
1.6%
partly blocked
0
0.0%
not blocked
124
98.4%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
8
6.3%
Forecast only
0
0.0%
No public exploit
118
93.7%
split by
peak 35 / year
20031
No exploit published1
High1
not blocked1
No public exploit1
20040
20050
20060
20070
20080
20090
20100
20110
20122
Protected by Waratek1
No exploit published1
High1
Medium1
blocked by ARMR today1
not blocked1
No public exploit2
20130
20140
20151
No exploit published1
Medium1
not blocked1
No public exploit1
20160
20175
Mitigation candidate1
No exploit published4
High1
Medium4
not blocked5
Proof of concept only1
No public exploit4
201813
No exploit published13
High7
Medium6
not blocked13
No public exploit13
201914
No exploit published14
Critical1
High6
Medium7
not blocked14
No public exploit14
202012
No exploit published12
Critical3
High4
Medium5
not blocked12
No public exploit12
20214
No exploit published4
High2
Medium2
not blocked4
No public exploit4
202217
No exploit published17
Critical2
High7
Medium8
not blocked17
Proof of concept only1
No public exploit16
202310
No exploit published10
High3
Medium6
Low1
not blocked10
Proof of concept only1
No public exploit9
20246
No exploit published6
High2
Medium4
not blocked6
No public exploit6
20256
No exploit published6
High4
Medium2
not blocked6
Proof of concept only1
No public exploit5
202635
Protected by Waratek1
Mitigation candidate1
No exploit published33
Critical10
High14
Medium10
Low1
blocked by ARMR today1
not blocked34
Proof of concept only4
No public exploit31
200420062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-10314 | Medium | 2019-04-30 | No exploit published | No public exploit | Jenkins Koji Plugin disables SSL/TLS and hostname verification globally for the Jenkins master JVM. |
| CVE-2018-20200 | Medium | 2019-04-18 | No exploit published | No public exploit | CertificatePinner.java in OkHttp 3.x through 3.12.0 allows man-in-the-middle attackers to bypass certificate pinning by changing SSLContext and the boolean values while hooking the application. NOTE: This id is disputed because some parties don't consider this is a vulnerability. Their rationale can be found in https://github.com/square/okhttp/issues/4967 |
| CVE-2019-1003009 | High | 2019-02-06 | No exploit published | No public exploit | An improper certificate validation vulnerability exists in Jenkins Active Directory Plugin 2.10 and earlier in src/main/java/hudson/plugins/active_directory/ActiveDirectoryDomain.java, src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java, src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java that allows attackers to impersonate the Active Directory server Jenkins connects to for authentication if Jenkins is configured to use StartTLS. |
| CVE-2018-1320 | High | 2019-01-07 | No exploit published | No public exploit | Apache Thrift Java client library versions 0.5.0 through 0.11.0 can bypass SASL negotiation isComplete validation in the org.apache.thrift.transport.TSaslTransport class. An assert used to determine if the SASL handshake had successfully completed could be disabled in production settings making the validation incomplete. |
| CVE-2018-17187 | High | 2018-11-13 | No exploit published | No public exploit | The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the 'transport.ssl(...)' methods. Unless a verification mode was explicitly configured, client and server modes previously defaulted as documented to not verifying a peer certificate, with options to configure this explicitly or select a certificate verification mode with or without hostname verification being performed. The latter hostname verifying mode was not implemented in Apache Qpid Proton-J versions 0.3 to 0.29.0, with attempts to use it resulting in an exception. This left only the option to verify the certificate is trusted, leaving such a client vulnerable to Man In The Middle (MITM) attack. Uses of the Proton-J protocol engine which do not utilise the optional transport TLS wrapper are not impacted, e.g. usage within Qpid JMS. Uses of Proton-J utilising the optional transport TLS wrapper layer that wish to enable hostname verification must be upgraded to version 0.30.0 or later and utilise the VerifyMode#VERIFY_PEER_NAME configuration, which is now the default for client mode usage unless configured otherwise. |
| CVE-2018-11087 | Medium | 2018-09-14 | No exploit published | No public exploit | Pivotal Spring AMQP, 1.x versions prior to 1.7.10 and 2.x versions prior to 2.0.6, expose a man-in-the-middle vulnerability due to lack of hostname validation. A malicious user that has the ability to intercept traffic would be able to view data in transit. |
| CVE-2018-11775 | High | 2018-09-10 | No exploit published | No public exploit | TLS hostname verification when using the Apache ActiveMQ Client before 5.15.6 was missing which could make the client vulnerable to a MITM attack between a Java application using the ActiveMQ client and the ActiveMQ server. This is now enabled by default. |
| CVE-2018-1999035 | High | 2018-08-01 | No exploit published | No public exploit | A man in the middle vulnerability exists in Jenkins Inedo BuildMaster Plugin 1.3 and earlier in BuildMasterConfiguration.java, BuildMasterConfig.java, BuildMasterApi.java that allows attackers to impersonate any service that Jenkins connects to. |
| CVE-2018-1999034 | High | 2018-08-01 | No exploit published | No public exploit | A man in the middle vulnerability exists in Jenkins Inedo ProGet Plugin 0.8 and earlier in ProGetApi.java, ProGetConfig.java, ProGetConfiguration.java that allows attackers to impersonate any service that Jenkins connects to. |
| CVE-2018-1999025 | High | 2018-08-01 | No exploit published | No public exploit | A man in the middle vulnerability exists in Jenkins TraceTronic ECU-TEST Plugin 2.3 and earlier in ATXPublisher.java, ATXValidator.java that allows attackers to impersonate any service that Jenkins connects to. |
| CVE-2018-10894 | Medium | 2018-08-01 | No exploit published | No public exploit | It was found that SAML authentication in Keycloak 3.4.3.Final incorrectly authenticated expired certificates. A malicious user could use this to access unauthorized data or possibly conduct further attacks. |
| CVE-2017-2649 | High | 2018-07-27 | No exploit published | No public exploit | It was found that the Active Directory Plugin for Jenkins up to and including version 2.2 did not verify certificates of the Active Directory server, thereby enabling Man-in-the-Middle attacks. |
| CVE-2017-2648 | Medium | 2018-07-27 | No exploit published | No public exploit | It was found that jenkins-ssh-slaves-plugin before version 1.15 did not perform host key verification, thereby enabling Man-in-the-Middle attacks. |
| CVE-2018-1000605 | High | 2018-06-26 | No exploit published | No public exploit | A man in the middle vulnerability exists in Jenkins CollabNet Plugin 2.0.4 and earlier in CollabNetApp.java, CollabNetPlugin.java, CNFormFieldValidator.java that allows attackers to impersonate any service that Jenkins connects to. |
| CVE-2018-1000151 | Medium | 2018-04-05 | No exploit published | No public exploit | A man in the middle vulnerability exists in Jenkins vSphere Plugin 2.16 and older in VSphere.java that disables SSL/TLS certificate validation by default. |
| CVE-2017-1000396 | Medium | 2018-01-26 | No exploit published | No public exploit | Jenkins 2.73.1 and earlier, 2.83 and earlier bundled a version of the commons-httpclient library with the vulnerability CVE-2012-6153 that incorrectly verified SSL certificates, making it susceptible to man-in-the-middle attacks. This library is widely used as a transitive dependency in Jenkins plugins. The fix for CVE-2012-6153 was backported to the version of commons-httpclient that is bundled in core and made available to plugins. |
| CVE-2014-3607 | Medium | 2018-01-08 | No exploit published | No public exploit | DefaultHostnameVerifier in Ldaptive (formerly vt-ldap) 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-2017-1000209 | Medium | 2017-11-17 | No exploit published | No public exploit | The Java WebSocket client nv-websocket-client 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/TLS servers via an arbitrary valid certificate. |
| CVE-2016-3083 | High | 2017-05-30 | No exploit published | No public exploit | Apache Hive (JDBC + HiveServer2) implements SSL for plain TCP and HTTP connections (it supports both transport modes). While validating the server's certificate during the connection setup, the client in Apache Hive before 1.2.2 and 2.0.x before 2.0.1 doesn't seem to be verifying the common name attribute of the certificate. In this way, if a JDBC client sends an SSL request to server abc.com, and the server responds with a valid certificate (certified by CA) but issued to xyz.com, the client will accept that as a valid certificate and the SSL handshake will go through. |
| CVE-2016-5016 | Medium | 2017-04-24 | No exploit published | No public exploit | Pivotal Cloud Foundry 239 and earlier, UAA (aka User Account and Authentication Server) 3.4.1 and earlier, UAA release 12.2 and earlier, PCF (aka Pivotal Cloud Foundry) Elastic Runtime 1.6.x before 1.6.35, and PCF Elastic Runtime 1.7.x before 1.7.13 does not validate if a certificate is expired. |
| CVE-2017-5653 | Medium | 2017-04-18 | No exploit published | No public exploit | JAX-RS XML Security streaming clients in Apache CXF before 3.1.11 and 3.0.13 do not validate that the service response was signed or encrypted, which allows remote attackers to spoof servers. |
| CVE-2016-2402 | Medium | 2017-01-30 | Mitigation candidate | Proof of concept only | OkHttp before 2.7.4 and 3.x before 3.1.2 allows man-in-the-middle attackers to bypass certificate pinning by sending a certificate chain with a certificate from a non-pinned trusted CA and the pinned certificate. |
| CVE-2015-1796 | Medium | 2015-07-08 | No exploit published | No public exploit | The PKIX trust engines in Shibboleth Identity Provider before 2.4.4 and OpenSAML Java (OpenSAML-J) before 2.6.5 trust candidate X.509 credentials when no trusted names are available for the entityID, which allows remote attackers to impersonate an entity via a certificate issued by a shibmd:KeyAuthority trust anchor. |
| CVE-2012-5817 | High | 2012-11-04 | No exploit published | No public exploit | Codehaus XFire 1.2.6 and earlier, as used in the Amazon EC2 API Tools Java library 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-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-2003-1229 | High | 2003-12-31 | No exploit published | No public exploit | X509TrustManager in (1) Java Secure Socket Extension (JSSE) in SDK and JRE 1.4.0 through 1.4.0_01, (2) JSSE before 1.0.3, (3) Java Plug-in SDK and JRE 1.3.0 through 1.4.1, and (4) Java Web Start 1.0 through 1.2 incorrectly calls the isClientTrusted method when determining server trust, which results in improper validation of digital certificate and allows remote attackers to (1) falsely authenticate peers for SSL or (2) incorrectly validate signed JAR files. |