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-2017-7678 Vulnerability in maven package org.apache.spark:spark-core
CVE-2017-5664 Vulnerability in maven package org.apache.tomcat:tomcat-catalina
CVE-2018-8025 Vulnerability in maven package org.apache.hbase:hbase-thrift
CVE-2020-13973 Vulnerability in maven package com.mikesamuel:json-sanitizer
CVE-2016-3081 Vulnerability in maven package org.apache.struts:struts2-core