Total
1040 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2019-11550 | 1 Citrix | 2 Netscaler Sd-wan, Sd-wan | 2024-11-21 | 4.3 MEDIUM | 5.9 MEDIUM |
Citrix SD-WAN 10.2.x before 10.2.1 and NetScaler SD-WAN 10.0.x before 10.0.7 have Improper Certificate Validation. | |||||
CVE-2019-11497 | 1 Couchbase | 1 Couchbase Server | 2024-11-21 | 5.0 MEDIUM | 7.5 HIGH |
In Couchbase Server 5.0.0, when an invalid Remote Cluster Certificate was entered as part of the reference creation, XDCR did not parse and check the certificate signature. It then accepted the invalid certificate and attempted to use it to establish future connections to the remote cluster. This has been fixed in version 5.5.0. XDCR now checks the validity of the certificate thoroughly and prevents a remote cluster reference from being created with an invalid certificate. | |||||
CVE-2019-11324 | 2 Canonical, Python | 2 Ubuntu Linux, Urllib3 | 2024-11-21 | 5.0 MEDIUM | 7.5 HIGH |
The urllib3 library before 1.24.2 for Python mishandles certain cases where the desired set of CA certificates is different from the OS store of CA certificates, which results in SSL connections succeeding in situations where a verification failure is the correct outcome. This is related to use of the ssl_context, ca_certs, or ca_certs_dir argument. | |||||
CVE-2019-11242 | 1 Cohesity | 1 Dataplatform | 2024-11-21 | 4.3 MEDIUM | 8.1 HIGH |
A man-in-the-middle vulnerability related to vCenter access was found in Cohesity DataPlatform version 5.x and 6.x prior to 6.1.1c. Cohesity clusters did not verify TLS certificates presented by vCenter. This vulnerability could expose Cohesity user credentials configured to access vCenter. | |||||
CVE-2019-10914 | 1 Matrixssl | 1 Matrixssl | 2024-11-21 | 7.5 HIGH | 9.8 CRITICAL |
pubRsaDecryptSignedElementExt in MatrixSSL 4.0.1 Open, as used in Inside Secure TLS Toolkit, has a stack-based buffer overflow during X.509 certificate verification because of missing validation in psRsaDecryptPubExt in crypto/pubkey/rsa_pub.c. | |||||
CVE-2019-10446 | 1 Jenkins | 1 Cadence Vmanager | 2024-11-21 | 6.4 MEDIUM | 8.2 HIGH |
Jenkins Cadence vManager Plugin 2.7.0 and earlier disabled SSL/TLS and hostname verification globally for the Jenkins master JVM. | |||||
CVE-2019-10444 | 1 Jenkins | 1 Bumblebee Hp Alm | 2024-11-21 | 6.4 MEDIUM | 6.5 MEDIUM |
Jenkins Bumblebee HP ALM Plugin 4.1.3 and earlier unconditionally disabled SSL/TLS and hostname verification for connections to HP ALM. | |||||
CVE-2019-10382 | 1 Jenkins | 1 Vmware Lab Manager Slaves | 2024-11-21 | 5.8 MEDIUM | 6.5 MEDIUM |
Jenkins VMware Lab Manager Slaves Plugin 0.2.8 and earlier disables SSL/TLS and hostname verification globally for the Jenkins master JVM. | |||||
CVE-2019-10381 | 1 Jenkins | 1 Codefresh Integration | 2024-11-21 | 4.3 MEDIUM | 7.5 HIGH |
Jenkins Codefresh Integration Plugin 1.8 and earlier disables SSL/TLS and hostname verification globally for the Jenkins master JVM. | |||||
CVE-2019-10334 | 1 Jenkins | 1 Electricflow | 2024-11-21 | 5.8 MEDIUM | 6.5 MEDIUM |
Jenkins ElectricFlow Plugin 1.1.5 and earlier disabled SSL/TLS and hostname verification globally for the Jenkins master JVM when MultipartUtility.java is used to upload files. | |||||
CVE-2019-10317 | 1 Jenkins | 1 Sitemonitor | 2024-11-21 | 4.3 MEDIUM | 5.9 MEDIUM |
Jenkins SiteMonitor Plugin 0.5 and earlier disabled SSL/TLS and hostname verification globally for the Jenkins master JVM. | |||||
CVE-2019-10314 | 1 Jenkins | 1 Koji | 2024-11-21 | 4.3 MEDIUM | 5.9 MEDIUM |
Jenkins Koji Plugin disables SSL/TLS and hostname verification globally for the Jenkins master JVM. | |||||
CVE-2019-10091 | 1 Apache | 1 Geode | 2024-11-21 | 4.0 MEDIUM | 7.4 HIGH |
When TLS is enabled with ssl-endpoint-identification-enabled set to true, Apache Geode fails to perform hostname verification of the entries in the certificate SAN during the SSL handshake. This could compromise intra-cluster communication using a man-in-the-middle attack. | |||||
CVE-2019-1010275 | 1 Helm | 1 Helm | 2024-11-21 | 7.5 HIGH | 9.8 CRITICAL |
helm Before 2.7.2 is affected by: CWE-295: Improper Certificate Validation. The impact is: Unauthorized clients could connect to the server because self-signed client certs were aloowed. The component is: helm (many files updated, see https://github.com/helm/helm/pull/3152/files/1096813bf9a425e2aa4ac755b6c991b626dfab50). The attack vector is: A malicious client could connect to the server over the network. The fixed version is: 2.7.2. | |||||
CVE-2019-1010206 | 1 Http Request Project | 1 Http Request | 2024-11-21 | 4.3 MEDIUM | 5.9 MEDIUM |
OSS Http Request (Apache Cordova Plugin) 6 is affected by: Missing SSL certificate validation. The impact is: certificate spoofing. The component is: use this library when https communication. The attack vector is: certificate spoofing. | |||||
CVE-2019-1003009 | 1 Jenkins | 1 Active Directory | 2024-11-21 | 5.8 MEDIUM | 7.4 HIGH |
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-2019-0054 | 1 Juniper | 25 Csrx, Junos, Srx100 and 22 more | 2024-11-21 | 5.8 MEDIUM | 6.8 MEDIUM |
An Improper Certificate Validation weakness in the SRX Series Application Identification (app-id) signature update client of Juniper Networks Junos OS allows an attacker to perform Man-in-the-Middle (MitM) attacks which may compromise the integrity and confidentiality of the device. This issue affects: Juniper Networks Junos OS 15.1X49 versions prior to 15.1X49-D120 on SRX Series devices. No other versions of Junos OS are affected. | |||||
CVE-2018-9127 | 1 Botan Project | 1 Botan | 2024-11-21 | 7.5 HIGH | 9.8 CRITICAL |
Botan 2.2.0 - 2.4.0 (fixed in 2.5.0) improperly handled wildcard certificates and could accept certain certificates as valid for hostnames when, under RFC 6125 rules, they should not match. This only affects certificates issued to the same domain as the host, so to impersonate a host one must already have a wildcard certificate matching other hosts in the same domain. For example, b*.example.com would match some hostnames that do not begin with a 'b' character. | |||||
CVE-2018-8970 | 1 Openbsd | 1 Libressl | 2024-11-21 | 5.8 MEDIUM | 7.4 HIGH |
The int_x509_param_set_hosts function in lib/libcrypto/x509/x509_vpm.c in LibreSSL 2.7.0 before 2.7.1 does not support a certain special case of a zero name length, which causes silent omission of hostname verification, and consequently allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate. NOTE: the LibreSSL documentation indicates that this special case is supported, but the BoringSSL documentation does not. | |||||
CVE-2018-8479 | 1 Microsoft | 2 C Software Development Kit, Java Software Development Kit | 2024-11-21 | 6.8 MEDIUM | 5.6 MEDIUM |
A spoofing vulnerability exists for the Azure IoT Device Provisioning for the C SDK library using the HTTP protocol on Windows platform, aka "Azure IoT SDK Spoofing Vulnerability." This affects C SDK. |