Description
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 "Allow self-signed certificates" 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's authentication mechanism.
Remediation
References
https://github.com/Graylog2/graylog2-server/issues/5906
Related Vulnerabilities
CVE-2016-10527 Vulnerability in npm package riot-compiler
CVE-2022-31183 Vulnerability in maven package co.fs2:fs2-io_sjs1_2.12
CVE-2022-41946 Vulnerability in maven package org.postgresql:postgresql
CVE-2019-10297 Vulnerability in maven package org.jenkins-ci.plugins:sametime
CVE-2019-10335 Vulnerability in maven package org.jenkins-ci.plugins:electricflow