CVE-2020-15813

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 v3 8.1 HIGH
CVSS v2.0 6.8 MEDIUM

8.1^/10

CVSS v3 : HIGH

Vector :

Exploitability : 2.2 / Impact : 5.9

Attack Vector NETWORK

Attack Complexity HIGH

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

6.8^/10

CVSS v2.0 : MEDIUM

Vector : AV:N/AC:M/Au:N/C:P/I:P/A:P

Exploitability : 8.6 / Impact : 6.4

Access Vector NETWORK

Access Complexity MEDIUM

Authentication NONE

Confidentiality Impact PARTIAL

Integrity Impact PARTIAL

Availability Impact PARTIAL

References

Link	Resource
https://github.com/Graylog2/graylog2-server/issues/5906	Third Party Advisory
https://github.com/Graylog2/graylog2-server/issues/5906	Third Party Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:graylog:graylog:*:*:*:*:*:*:*:*

History

21 Nov 2024, 05:06

Type	Values Removed	Values Added
References	~~() https://github.com/Graylog2/graylog2-server/issues/5906 - Third Party Advisory~~	() https://github.com/Graylog2/graylog2-server/issues/5906 - Third Party Advisory

Information

Published : 2020-07-17 19:15

Updated : 2024-11-21 05:06

NVD link : CVE-2020-15813

Mitre link : CVE-2020-15813

CVE.ORG link : CVE-2020-15813

JSON object : View

Products Affected

graylog

graylog

CWE

CWE-295

Improper Certificate Validation

{"id": "CVE-2020-15813", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 6.8, "accessVector": "NETWORK", "vectorString": "AV:N/AC:M/Au:N/C:P/I:P/A:P", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "MEDIUM", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 6.4, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 8.6, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.2}]}, "published": "2020-07-17T19:15:12.547", "references": [{"url": "https://github.com/Graylog2/graylog2-server/issues/5906", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://github.com/Graylog2/graylog2-server/issues/5906", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-295"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Graylog versiones anteriores a 3.3.3, carece de una comprobaci\u00f3n de certificado SSL para servidores LDAP. Permite el uso de una base de datos de usuarios y grupos externos almacenados en LDAP. La configuraci\u00f3n de la conexi\u00f3n permite el uso de conexiones sin cifrar, con seguridad SSL o TLS. Desafortunadamente, el c\u00f3digo del cliente Graylog (en todas las versiones que admiten LDAP) no implementa una comprobaci\u00f3n de certificado adecuada (independientemente de si se usa la opci\u00f3n \"Allow self-signed certificates\"). Por lo tanto, cualquier atacante con la capacidad de interceptar el tr\u00e1fico de red entre un servidor Graylog y un servidor LDAP puede redireccionar el tr\u00e1fico hacia un servidor LDAP diferente (desapercibido por el servidor Graylog debido a la falta de comprobaci\u00f3n del certificado), omitiendo efectivamente el mecanismo de autenticaci\u00f3n de Graylog"}], "lastModified": "2024-11-21T05:06:13.953", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:graylog:graylog:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "F9A21A46-6422-4E60-ADAA-9605AB691F95", "versionEndExcluding": "3.3.3"}], "operator": "OR"}]}], "sourceIdentifier": "cve@mitre.org"}