First published: Thu Oct 26 2023(Updated: )
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.
Credit: bressers@elastic.co
Affected Software | Affected Version | How to fix |
---|---|---|
Elastic Elastic Beats | >=8.0.0<=8.9.2 | |
Elastic Elastic Agent | >=8.0.0<=8.9.2 | |
Elastic Apm Server | >=8.0.0<=8.9.2 | |
Elastic Elastic Fleet Server | >=8.0.0<=8.9.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-31421 is a vulnerability that affects Beats, Elastic Agent, APM Server, and Fleet Server, allowing for improper certificate validation.
The vulnerability allows for the possibility of the server certificate not being validated for the target IP address.
Versions between 8.0.0 and 8.9.2 of Beats, Elastic Agent, APM Server, and Fleet Server are affected by CVE-2023-31421.
CVE-2023-31421 has a severity rating of 7.5, which is considered high.
To fix the vulnerability, it is recommended to update the affected software to version 8.10.1 or later.