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.
Metrics
Affected Vendors & Products
References
Link | Providers |
---|---|
https://github.com/Graylog2/graylog2-server/issues/5906 |
History
No history.
MITRE
Status: PUBLISHED
Assigner: mitre
Published: 2020-07-17T18:05:06
Updated: 2024-08-04T13:30:21.870Z
Reserved: 2020-07-17T00:00:00
Link: CVE-2020-15813
Vulnrichment
No data.
NVD
Status : Modified
Published: 2020-07-17T19:15:12.547
Modified: 2024-11-21T05:06:13.953
Link: CVE-2020-15813
Redhat
No data.