{"id":"CVE-2020-15813","aliases":["EUVD-2022-0790","GHSA-3gg9-f3vh-866f"],"status":"published","title":"Improper Certificate Validation in Graylog","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.","severity":{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-12","score":0.00779,"percentile":0.56386,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-295"],"published":"2020-07-17T18:05:06Z","modified":"2026-10-20T10:51:56Z","fixes":[{"ecosystem":"Maven","package":"org.graylog:graylog-parent","fixed_in":["3.3.3"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.graylog:graylog-parent","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.3"}]}]},{"source":"osv","ecosystem":"Maven","package":"org.graylog:graylog-parent","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.3"}]}],"versions":["2.2.0","2.2.0-alpha.1","2.2.0-alpha.2","2.2.0-alpha.3","2.2.0-alpha.4","2.2.0-beta.1","2.2.0-beta.2","2.2.0-beta.3","2.2.0-beta.4","2.2.0-beta.5","2.2.0-beta.6","2.2.0-rc.1","2.2.1","2.2.2","2.2.3","2.3.0","2.3.0-alpha.1","2.3.0-alpha.2","2.3.0-alpha.3","2.3.0-beta.1","2.3.0-rc.1","2.3.0-rc.2","2.3.1","2.3.2","2.4.0","2.4.0-alpha.1","2.4.0-alpha.2","2.4.0-alpha.3","2.4.0-beta.1","2.4.0-beta.2","2.4.0-beta.3","2.4.0-beta.4","2.4.0-rc.1","2.4.0-rc.2","2.4.1","2.4.2","2.4.3","2.4.4","2.4.5","2.4.6","2.4.7","2.5.0","2.5.0-alpha.1","2.5.0-beta.1","2.5.1","2.5.2","3.0.0","3.0.0-alpha.0","3.0.0-alpha.1","3.0.0-alpha.2","3.0.0-alpha.3","3.0.0-alpha.4","3.0.0-alpha.5","3.0.0-beta.1","3.0.0-beta.2","3.0.0-beta.4","3.0.0-rc.1","3.0.0-rc.2","3.0.1","3.0.2","3.1.0","3.1.0-beta.2","3.1.0-beta.3","3.1.0-rc.1","3.1.0-rc.2","3.1.1","3.1.2","3.1.3","3.1.4","3.2.0","3.2.1","3.2.2","3.2.3","3.2.4","3.2.5","3.3.0","3.3.0-beta.3","3.3.0-rc.1","3.3.2"]}],"products":[{"vendor":"graylog","product":"graylog"}],"references":[{"url":"https://github.com/Graylog2/graylog2-server/issues/5906","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15813","tags":["advisory"]},{"url":"https://github.com/Graylog2/graylog2-server/pull/8569","tags":["web"]},{"url":"https://github.com/advisories/GHSA-3gg9-f3vh-866f"}],"sources":{"cve":[{"id":"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.","status":"published","published":"2020-07-17T18:05:06Z","modified":"2024-08-04T13:30:21.87Z","updated_at":"2026-11-02T14:35:50.228781Z"}],"euvd":[{"id":"EUVD-2022-0790","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.","status":"published","published":"2020-07-17T18:05:06Z","modified":"2024-08-04T13:30:21Z","updated_at":"2026-11-03T03:07:30.36726Z"}],"ghsa":[{"id":"GHSA-3gg9-f3vh-866f","title":"Improper Certificate Validation in Graylog","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.","status":"published","published":"2022-02-10T22:39:58Z","modified":"2023-02-01T05:05:29Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-295"],"updated_at":"2026-11-02T14:36:34.260786Z"}],"nvd":[{"id":"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.","status":"published","published":"2020-07-17T19:15:12.547Z","modified":"2026-06-17T02:57:14.26Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":6.8,"vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-295"],"updated_at":"2026-11-02T14:06:10.086163Z"}],"osv":[{"id":"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.","status":"published","published":"2020-07-17T19:15:12.547Z","modified":"2026-10-20T10:51:56.282075207Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:14.828228Z"},{"id":"GHSA-3gg9-f3vh-866f","title":"Improper Certificate Validation in Graylog","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.","status":"published","published":"2022-02-10T22:39:58Z","modified":"2023-11-08T04:02:38.210527Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-295"],"updated_at":"2026-11-02T15:46:35.747385Z"}]}}