CVE-2020-15813
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.
How to fix
- graylog graylog3.3.3 or later
- org.graylog:graylog-parent3.3.3 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| graylog graylog | v < 3.3.3 | 3.3.3 |
| org.graylog:graylog-parentMaven | v < 3.3.3 | 3.3.3 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.