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.
| Software | From | Fixed in |
|---|---|---|
| elastic / elastic_beats | 8.0.0 | 8.9.2.x |
| elastic / elastic_agent | 8.0.0 | 8.9.2.x |
| elastic / elastic_fleet_server | 8.0.0 | 8.9.2.x |
| elastic / apm_server | 8.0.0 | 8.9.2.x |