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.

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.

Уязвимость агента для сборки и доставки данных в Elasticsearch или Logstash Elastic Beats, агента для сбора метрик Elastic Agent, серверного программного средства мониторинга и анализа производительности приложений Elastic APM Server, серверного программного средства управление агентами Elastic Agent Elastic Fleet Server, связанная с ошибками процедуры подтверждения подлинности TLS сертификата, позволяющая нарушителю установить соединение с недействительным сертификатом сервера