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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
org.graylog:graylog-parentMaven | < 3.3.3 | 3.3.3 |
Affected products
3- Graylog/Graylogdescription
Patches
Vulnerability mechanics
References
4- github.com/Graylog2/graylog2-server/issues/5906nvdThird Party AdvisoryWEB
- github.com/advisories/GHSA-3gg9-f3vh-866fghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2020-15813ghsaADVISORY
- github.com/Graylog2/graylog2-server/pull/8569ghsaWEB
News mentions
0No linked articles in our index yet.