https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 16 Oct 2026 11:46:55 +0000 https://cve.radiocsirt.org/vuln/cnvd-2020-44618 cnvd-2020-44618 https://cve.radiocsirt.org/vuln/cnvd-2020-44618 https://cve.radiocsirt.org/vuln/euvd-2026-43175 EUVD-2026-43175 https://cve.radiocsirt.org/vuln/euvd-2026-43175 https://cve.radiocsirt.org/vuln/fkie_cve-2020-15813 <p>Graylog before 3.3.3 lacks SSL Certificate Validation for LDAP servers. It allows use of an external user/group database stored in LDAP. The connection configuration allows the usage of unencrypted, SSL- or TLS-secured connections. Unfortunately, the Graylog client code (in all versions that support LDAP) does not implement proper certificate validation (regardless of whether the &#34;Allow self-signed certificates&#34; option is used). Therefore, any attacker with the ability to intercept network traffic between a Graylog server and an LDAP server is able to redirect traffic to a different LDAP server (unnoticed by the Graylog server due to the lack of certificate validation), effectively bypassing Graylog&#39;s authentication mechanism.</p> <p>Graylog before 3.3.3 lacks SSL Certificate Validation for LDAP servers. It allows use of an external user/group database stored in LDAP. The connection configuration allows the usage of unencrypted, SSL- or TLS-secured connections. Unfortunately, the Graylog client code (in all versions that support LDAP) does not implement proper certificate validation (regardless of whether the &#34;Allow self-signed certificates&#34; option is used). Therefore, any attacker with the ability to intercept network traffic between a Graylog server and an LDAP server is able to redirect traffic to a different LDAP server (unnoticed by the Graylog server due to the lack of certificate validation), effectively bypassing Graylog&#39;s authentication mechanism.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-15813 https://cve.radiocsirt.org/vuln/ghsa-3gg9-f3vh-866f <p><strong>Affected:</strong> Maven: org.graylog:graylog-parent</p> <p>Graylog before 3.3.3 lacks SSL Certificate Validation for LDAP servers. It allows use of an external user/group database stored in LDAP. The connection configuration allows the usage of unencrypted, SSL- or TLS-secured connections. Unfortunately, the Graylog client code (in all versions that support LDAP) does not implement proper certificate validation (regardless of whether the &#34;Allow self-signed certificates&#34; option is used). Therefore, any attacker with the ability to intercept network traffic between a Graylog server and an LDAP server is able to redirect traffic to a different LDAP server (unnoticed by the Graylog server due to the lack of certificate validation), effectively bypassing Graylog&#39;s authentication mechanism.</p> <p><strong>Affected:</strong> Maven: org.graylog:graylog-parent</p> <p>Graylog before 3.3.3 lacks SSL Certificate Validation for LDAP servers. It allows use of an external user/group database stored in LDAP. The connection configuration allows the usage of unencrypted, SSL- or TLS-secured connections. Unfortunately, the Graylog client code (in all versions that support LDAP) does not implement proper certificate validation (regardless of whether the &#34;Allow self-signed certificates&#34; option is used). Therefore, any attacker with the ability to intercept network traffic between a Graylog server and an LDAP server is able to redirect traffic to a different LDAP server (unnoticed by the Graylog server due to the lack of certificate validation), effectively bypassing Graylog&#39;s authentication mechanism.</p> https://cve.radiocsirt.org/vuln/ghsa-3gg9-f3vh-866f https://cve.radiocsirt.org/vuln/gsd-2020-15813 gsd-2020-15813 https://cve.radiocsirt.org/vuln/gsd-2020-15813