CVE-2023-31421

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

Configuration 1 (hide)

cpe:2.3:a:elastic:elastic_beats:*:*:*:*:*:*:*:*

Configuration 2 (hide)

cpe:2.3:a:elastic:elastic_agent:*:*:*:*:*:*:*:*

Configuration 3 (hide)

cpe:2.3:a:elastic:apm_server:*:*:*:*:*:*:*:*

Configuration 4 (hide)

cpe:2.3:a:elastic:elastic_fleet_server:*:*:*:*:*:*:*:*

History

15 Feb 2024, 19:39

Type Values Removed Values Added
New CVE

Information

Published : 2023-10-26 04:15

Updated : 2024-02-15 19:39


NVD link : CVE-2023-31421

Mitre link : CVE-2023-31421

CVE.ORG link : CVE-2023-31421


JSON object : View

Products Affected

elastic

  • elastic_agent
  • elastic_fleet_server
  • elastic_beats
  • apm_server
CWE
CWE-295

Improper Certificate Validation