title: Beats, Elastic Agent, APM Server, and Fleet Server Improper Certificate Validation issue
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.
problem types: CWE-295: Improper Certificate Validation
affected:
{
defaultStatus: unaffected
product: Beats
vendor: Elastic
versions:
status: affected, version: 8.0.0, 8.9.2
}
{
defaultStatus: unaffected
product: Elastic Agent
vendor: Elastic
versions:
status: affected, version: 8.0.0, 8.9.2
}
{
defaultStatus: unaffected
product: APM Server
vendor: Elastic
versions:
status: affected, version: 8.0.0, 8.9.2
}
{
defaultStatus: unaffected
product: Fleet Server
vendor: Elastic
versions:
status: affected, version: 8.0.0, 8.9.2
}
metrics:
cvssV3_1: [
attackComplexity: HIGH
attackVector: NETWORK
availabilityImpact: NONE
baseScore: 5.9
baseSeverity: MEDIUM
confidentialityImpact: HIGH
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
version: 3.1
]
format: CVSS
scenarios: GENERAL