CVE-2020-26214

{"id": "CVE-2020-26214", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "[email protected]", "cvssData": {"version": "2.0", "baseScore": 7.5, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:N/C:P/I:P/A:P", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "LOW", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 6.4, "baseSeverity": "HIGH", "obtainAllPrivilege": false, "exploitabilityScore": 10.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Secondary", "source": "[email protected]", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.1, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 3.9}, {"type": "Primary", "source": "[email protected]", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 3.9}]}, "published": "2020-11-06T18:15:12.437", "references": [{"url": "https://github.com/alerta/alerta/commit/2bfa31779a4c9df2fa68fa4d0c5c909698c5ef65", "tags": ["Patch", "Third Party Advisory"], "source": "[email protected]"}, {"url": "https://github.com/alerta/alerta/issues/1277", "tags": ["Third Party Advisory"], "source": "[email protected]"}, {"url": "https://github.com/alerta/alerta/pull/1345", "tags": ["Third Party Advisory"], "source": "[email protected]"}, {"url": "https://github.com/alerta/alerta/security/advisories/GHSA-5hmm-x8q8-w5jh", "tags": ["Third Party Advisory"], "source": "[email protected]"}, {"url": "https://pypi.org/project/alerta-server/8.1.0/", "tags": ["Third Party Advisory"], "source": "[email protected]"}, {"url": "https://tools.ietf.org/html/rfc4513#section-5.1.2", "tags": ["Third Party Advisory"], "source": "[email protected]"}, {"url": "https://github.com/alerta/alerta/commit/2bfa31779a4c9df2fa68fa4d0c5c909698c5ef65", "tags": ["Patch", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/alerta/alerta/issues/1277", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/alerta/alerta/pull/1345", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/alerta/alerta/security/advisories/GHSA-5hmm-x8q8-w5jh", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://pypi.org/project/alerta-server/8.1.0/", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://tools.ietf.org/html/rfc4513#section-5.1.2", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "[email protected]", "description": [{"lang": "en", "value": "CWE-287"}]}], "descriptions": [{"lang": "en", "value": "In Alerta before version 8.1.0, users may be able to bypass LDAP authentication if they provide an empty password when Alerta server is configure to use LDAP as the authorization provider. Only deployments where LDAP servers are configured to allow unauthenticated authentication mechanism for anonymous authorization are affected. A fix has been implemented in version 8.1.0 that returns HTTP 401 Unauthorized response for any authentication attempts where the password field is empty. As a workaround LDAP administrators can disallow unauthenticated bind requests by clients."}, {"lang": "es", "value": "En Alerta versiones anteriores a 8.1.0, los usuarios pueden ser capaces de omitir la autenticaci\u00f3n LDAP si proporcionan una contrase\u00f1a vac\u00eda cuando el servidor de Alerta est\u00e1 configurado para usar LDAP como proveedor de autorizaci\u00f3n. Solo est\u00e1n afectadas las implementaciones en las que los servidores LDAP est\u00e1n configurados para permitir un mecanismo de autenticaci\u00f3n no autenticado para la autorizaci\u00f3n an\u00f3nima. Una correcci\u00f3n ha sido implementada en la versi\u00f3n 8.1.0, que devuelve una respuesta HTTP 401 no autorizada para cualquier intento de autenticaci\u00f3n donde el campo de contrase\u00f1a est\u00e1 vac\u00edo. Como soluci\u00f3n alternativa, los administradores de LDAP pueden rechazar las peticiones de vinculaci\u00f3n no autenticadas de los clientes"}], "lastModified": "2024-11-21T05:19:32.727", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:alerta_project:alerta:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "2C53AE9D-6FD9-4608-BD7E-9AF7088726E6", "versionEndExcluding": "7.5.7"}, {"criteria": "cpe:2.3:a:alerta_project:alerta:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "C22E7117-7A0F-4B6C-A0D7-717D92653221", "versionEndExcluding": "8.1.0", "versionStartIncluding": "8.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "[email protected]"}