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.
References
Configurations
History
21 Nov 2024, 08:01
Type | Values Removed | Values Added |
---|---|---|
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.9 |
References | () https://discuss.elastic.co/t/beats-elastic-agent-apm-server-and-fleet-server-8-10-1-security-update-improper-certificate-validation-issue-esa-2023-16/343385 - Vendor Advisory | |
References | () https://www.elastic.co/community/security - Vendor Advisory |
15 Feb 2024, 19:39
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2023-10-26 04:15
Updated : 2024-11-21 08:01
NVD link : CVE-2023-31421
Mitre link : CVE-2023-31421
CVE.ORG link : CVE-2023-31421
JSON object : View
Products Affected
elastic
- apm_server
- elastic_fleet_server
- elastic_agent
- elastic_beats
CWE
CWE-295
Improper Certificate Validation