Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Graylog | Graylog | < 3.3.3 |
Related Weaknesses (CWE)
References
- https://github.com/Graylog2/graylog2-server/issues/5906Third Party Advisory
- https://github.com/Graylog2/graylog2-server/issues/5906Third Party Advisory
FAQ
What is CVE-2020-15813?
CVE-2020-15813 is a vulnerability with a CVSS score of 8.1 (HIGH). 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, S...
How severe is CVE-2020-15813?
CVE-2020-15813 has been rated HIGH with a CVSS base score of 8.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2020-15813?
Check the references section above for vendor advisories and patch information. Affected products include: Graylog Graylog.