Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| 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 |
Related Weaknesses (CWE)
References
- https://discuss.elastic.co/t/beats-elastic-agent-apm-server-and-fleet-server-8-1Vendor Advisory
- https://www.elastic.co/community/securityVendor Advisory
- https://discuss.elastic.co/t/beats-elastic-agent-apm-server-and-fleet-server-8-1Vendor Advisory
- https://www.elastic.co/community/securityVendor Advisory
FAQ
What is CVE-2023-31421?
CVE-2023-31421 is a vulnerability with a CVSS score of 5.9 (MEDIUM). 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, certifi...
How severe is CVE-2023-31421?
CVE-2023-31421 has been rated MEDIUM with a CVSS base score of 5.9/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2023-31421?
Check the references section above for vendor advisories and patch information. Affected products include: Elastic Elastic Beats, Elastic Elastic Agent, Elastic Apm Server, Elastic Elastic Fleet Server.