CWE-295 Archives - CVE Vulnerability https://cvevulnerability.com/cwe_categories/cwe-295/ Sun, 26 Feb 2023 09:07:56 +0000 en-US hourly 1 https://wordpress.org/?v=7.0 https://cvevulnerability.com/wp-content/uploads/2023/02/cropped-Screenshot-2023-02-27-at-3.52.32-PM-32x32.png CWE-295 Archives - CVE Vulnerability https://cvevulnerability.com/cwe_categories/cwe-295/ 32 32 CVE-2007-5967 https://cvevulnerability.com/cve_vulnerabilities/cve-2007-5967/ Sun, 26 Feb 2023 09:07:56 +0000 https://www.cvevulnerability.com/cve_vulnerabilities/cve-2007-5967/ A flaw in Mozilla’s embedded certificate code might allow web sites to install root certificates on devices without user approval.

The post CVE-2007-5967 appeared first on CVE Vulnerability.

]]> A flaw in Mozilla’s embedded certificate code might allow web sites to install root certificates on devices without user approval.

The post CVE-2007-5967 appeared first on CVE Vulnerability.

]]> CVE-2018-9127 https://cvevulnerability.com/cve_vulnerabilities/cve-2018-9127/ Sun, 26 Feb 2023 06:51:44 +0000 https://www.cvevulnerability.com/cve_vulnerabilities/cve-2018-9127/ 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 […]

The post CVE-2018-9127 appeared first on CVE Vulnerability.

]]> 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.

The post CVE-2018-9127 appeared first on CVE Vulnerability.

]]> CVE-2018-8970 https://cvevulnerability.com/cve_vulnerabilities/cve-2018-8970/ Sun, 26 Feb 2023 06:51:41 +0000 https://www.cvevulnerability.com/cve_vulnerabilities/cve-2018-8970/ 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 […]

The post CVE-2018-8970 appeared first on CVE Vulnerability.

]]> 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.

The post CVE-2018-8970 appeared first on CVE Vulnerability.

]]> CVE-2018-8479 https://cvevulnerability.com/cve_vulnerabilities/cve-2018-8479/ Sun, 26 Feb 2023 06:51:28 +0000 https://www.cvevulnerability.com/cve_vulnerabilities/cve-2018-8479/ 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.

The post CVE-2018-8479 appeared first on CVE Vulnerability.

]]> 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.

The post CVE-2018-8479 appeared first on CVE Vulnerability.

]]> CVE-2018-8356 https://cvevulnerability.com/cve_vulnerabilities/cve-2018-8356/ Sun, 26 Feb 2023 06:51:25 +0000 https://www.cvevulnerability.com/cve_vulnerabilities/cve-2018-8356/ A security feature bypass vulnerability exists when Microsoft .NET Framework components do not correctly validate certificates, aka “.NET Framework Security Feature Bypass Vulnerability.” This affects .NET Framework 4.7.2, Microsoft .NET Framework 3.0, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2, ASP.NET Core 1.1, Microsoft .NET Framework 4.5.2, ASP.NET Core 2.0, ASP.NET Core 1.0, .NET Core 1.1, Microsoft .NET Framework […]

The post CVE-2018-8356 appeared first on CVE Vulnerability.

]]> A security feature bypass vulnerability exists when Microsoft .NET Framework components do not correctly validate certificates, aka “.NET Framework Security Feature Bypass Vulnerability.” This affects .NET Framework 4.7.2, Microsoft .NET Framework 3.0, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2, ASP.NET Core 1.1, Microsoft .NET Framework 4.5.2, ASP.NET Core 2.0, ASP.NET Core 1.0, .NET Core 1.1, Microsoft .NET Framework 3.5, Microsoft .NET Framework 3.5.1, Microsoft .NET Framework 4.6/4.6.1/4.6.2, .NET Core 1.0, .NET Core 2.0, Microsoft .NET Framework 4.6, Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.1/4.7.2, Microsoft .NET Framework 4.7.2.

The post CVE-2018-8356 appeared first on CVE Vulnerability.

]]> CVE-2018-8119 https://cvevulnerability.com/cve_vulnerabilities/cve-2018-8119/ Sun, 26 Feb 2023 06:51:18 +0000 https://www.cvevulnerability.com/cve_vulnerabilities/cve-2018-8119/ A spoofing vulnerability exists when the Azure IoT Device Provisioning AMQP Transport library improperly validates certificates over the AMQP protocol, aka “Azure IoT SDK Spoofing Vulnerability.” This affects C# SDK, C SDK, Java SDK.

The post CVE-2018-8119 appeared first on CVE Vulnerability.

]]> A spoofing vulnerability exists when the Azure IoT Device Provisioning AMQP Transport library improperly validates certificates over the AMQP protocol, aka “Azure IoT SDK Spoofing Vulnerability.” This affects C# SDK, C SDK, Java SDK.

The post CVE-2018-8119 appeared first on CVE Vulnerability.

]]> CVE-2018-8034 https://cvevulnerability.com/cve_vulnerabilities/cve-2018-8034/ Sun, 26 Feb 2023 06:51:16 +0000 https://www.cvevulnerability.com/cve_vulnerabilities/cve-2018-8034/ The host name verification when using TLS with the WebSocket client was missing. It is now enabled by default. Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.9, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, and 7.0.35 to 7.0.88.

The post CVE-2018-8034 appeared first on CVE Vulnerability.

]]> The host name verification when using TLS with the WebSocket client was missing. It is now enabled by default. Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.9, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, and 7.0.35 to 7.0.88.

The post CVE-2018-8034 appeared first on CVE Vulnerability.

]]> CVE-2018-8059 https://cvevulnerability.com/cve_vulnerabilities/cve-2018-8059/ Sun, 26 Feb 2023 06:51:16 +0000 https://www.cvevulnerability.com/cve_vulnerabilities/cve-2018-8059/ The Djelibeybi configuration examples for use of NGINX in SUSE Portus 2.3, when applied to certain configurations involving Docker Compose, have a Missing SSL Certificate Validation issue because no proxy_ssl_* directives are used.

The post CVE-2018-8059 appeared first on CVE Vulnerability.

]]> The Djelibeybi configuration examples for use of NGINX in SUSE Portus 2.3, when applied to certain configurations involving Docker Compose, have a Missing SSL Certificate Validation issue because no proxy_ssl_* directives are used.

The post CVE-2018-8059 appeared first on CVE Vulnerability.

]]> CVE-2018-8019 https://cvevulnerability.com/cve_vulnerabilities/cve-2018-8019/ Sun, 26 Feb 2023 06:51:15 +0000 https://www.cvevulnerability.com/cve_vulnerabilities/cve-2018-8019/ When using an OCSP responder Apache Tomcat Native 1.2.0 to 1.2.16 and 1.1.23 to 1.1.34 did not correctly handle invalid responses. This allowed for revoked client certificates to be incorrectly identified. It was therefore possible for users to authenticate with revoked certificates when using mutual TLS. Users not using OCSP checks are not affected by […]

The post CVE-2018-8019 appeared first on CVE Vulnerability.

]]> When using an OCSP responder Apache Tomcat Native 1.2.0 to 1.2.16 and 1.1.23 to 1.1.34 did not correctly handle invalid responses. This allowed for revoked client certificates to be incorrectly identified. It was therefore possible for users to authenticate with revoked certificates when using mutual TLS. Users not using OCSP checks are not affected by this vulnerability.

The post CVE-2018-8019 appeared first on CVE Vulnerability.

]]> CVE-2018-8020 https://cvevulnerability.com/cve_vulnerabilities/cve-2018-8020/ Sun, 26 Feb 2023 06:51:15 +0000 https://www.cvevulnerability.com/cve_vulnerabilities/cve-2018-8020/ Apache Tomcat Native 1.2.0 to 1.2.16 and 1.1.23 to 1.1.34 has a flaw that does not properly check OCSP pre-produced responses, which are lists (multiple entries) of certificate statuses. Subsequently, revoked client certificates may not be properly identified, allowing for users to authenticate with revoked certificates to connections that require mutual TLS. Users not using […]

The post CVE-2018-8020 appeared first on CVE Vulnerability.

]]> Apache Tomcat Native 1.2.0 to 1.2.16 and 1.1.23 to 1.1.34 has a flaw that does not properly check OCSP pre-produced responses, which are lists (multiple entries) of certificate statuses. Subsequently, revoked client certificates may not be properly identified, allowing for users to authenticate with revoked certificates to connections that require mutual TLS. Users not using OCSP checks are not affected by this vulnerability.

The post CVE-2018-8020 appeared first on CVE Vulnerability.

]]>