How severe is CVE-2023-31421?

This vulnerability has a severity rating of HIGH with a CVSS score of 7.5 out of 10.

What type of vulnerability is CVE-2023-31421?

This is classified as CWE-295, which is a common weakness in software security.

CVE-2023-31421 - HIGH Severity | CVSS 7.5

Vulnerability Description

It was discovered that when acting as TLS clients, Beats, Elastic Agent, APM Server, and Fleet Server did not verify whether the server certificate is valid for the target IP address; however, certificate signature validation is still performed. More specifically, when the client is configured to connect to an IP address (instead of a hostname) it does not validate the server certificate's IP SAN values against that IP address and certificate validation fails, and therefore the connection is not blocked as expected.

Related Vulnerabilities

CVE-2009-3046

HIGH

CVSS:7.5(High)

Opera before 10.00 does not check all intermediate X.509 certificates for revocation, which makes it easier for remote SSL servers to bypass validation of the certificate chain via a revoked certifica...

CWE-2952009

CVE-2009-4123

HIGH

CVSS:7.5(High)

The jruby-openssl gem before 0.6 for JRuby mishandles SSL certificate validation.

CWE-2952009

CVE-2012-5518

HIGH

CVSS:7.5(High)

vdsm: certificate generation upon node creation allowing vdsm to start and serve requests from anyone who has a matching key (and certificate)

CWE-2952012

CVE-2012-6071

HIGH

CVSS:7.5(High)

nuSOAP before 0.7.3-5 does not properly check the hostname of a cert.

CWE-2952012

CVE-2013-0264

HIGH

CVSS:7.5(High)

An import error was introduced in Cumin in the code refactoring in r5310. Server certificate validation is always disabled when connecting to Aviary servers, even if the installed packages on a system...

CWE-2952013

CVE-2013-7450

HIGH

CVSS:7.5(High)

Pulp before 2.3.0 uses the same the same certificate authority key and certificate for all installations.

CWE-2952013