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.
{
"cwe_ids": [
"CWE-295"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/31xxx/CVE-2023-31421.json",
"cna_assigner": "elastic",
"unresolved_ranges": [
{
"extracted_events": [
{
"introduced": "8.0.0, 8.9.2"
},
{
"last_affected": "8.0.0, 8.9.2"
},
{
"introduced": "8.0.0, 8.9.2"
},
{
"last_affected": "8.0.0, 8.9.2"
},
{
"introduced": "8.0.0, 8.9.2"
},
{
"last_affected": "8.0.0, 8.9.2"
},
{
"introduced": "8.0.0, 8.9.2"
},
{
"last_affected": "8.0.0, 8.9.2"
}
],
"source": "AFFECTED_FIELD"
}
]
}{
"cpe": "cpe:2.3:a:elastic:elastic_agent:*:*:*:*:*:*:*:*",
"source": "CPE_RANGE",
"extracted_events": [
{
"introduced": "8.0.0"
},
{
"last_affected": "8.9.2"
}
]
}