https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 18:27:20 +0000 https://cve.radiocsirt.org/vuln/bdu:2023-08099 bdu:2023-08099 https://cve.radiocsirt.org/vuln/bdu:2023-08099 https://cve.radiocsirt.org/vuln/certfr-2023-avi-0765 certfr-2023-avi-0765 https://cve.radiocsirt.org/vuln/certfr-2023-avi-0765 https://cve.radiocsirt.org/vuln/euvd-2026-8486 EUVD-2026-8486 https://cve.radiocsirt.org/vuln/euvd-2026-8486 https://cve.radiocsirt.org/vuln/fkie_cve-2023-31421 <p>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&#39;s IP SAN values against that IP address and certificate validation fails, and therefore the connection is not blocked as expected.</p> <p>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&#39;s IP SAN values against that IP address and certificate validation fails, and therefore the connection is not blocked as expected.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-31421 https://cve.radiocsirt.org/vuln/ghsa-4x46-8gg7-f9vx <p>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&#39;s IP SAN values against that IP address and certificate validation fails, and therefore the connection is not blocked as expected.</p> <p>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&#39;s IP SAN values against that IP address and certificate validation fails, and therefore the connection is not blocked as expected.</p> https://cve.radiocsirt.org/vuln/ghsa-4x46-8gg7-f9vx https://cve.radiocsirt.org/vuln/gsd-2023-31421 gsd-2023-31421 https://cve.radiocsirt.org/vuln/gsd-2023-31421