CVE-2020-4071

{"id": "CVE-2020-4071", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 2.1, "accessVector": "LOCAL", "vectorString": "AV:L/AC:L/Au:N/C:P/I:N/A:N", "authentication": "NONE", "integrityImpact": "NONE", "accessComplexity": "LOW", "availabilityImpact": "NONE", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 2.9, "baseSeverity": "LOW", "obtainAllPrivilege": false, "exploitabilityScore": 3.9, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 2.2, "attackVector": "PHYSICAL", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 0.5}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 2.4, "attackVector": "PHYSICAL", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 0.9}]}, "published": "2020-06-24T13:15:11.833", "references": [{"url": "https://github.com/tm-kn/django-basic-auth-ip-whitelist/security/advisories/GHSA-m38j-pmg3-v5x5", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://groups.google.com/forum/#%21msg/django-developers/iAaq0pvHXuA/fpUuwjK3i2wJ", "source": "security-advisories@github.com"}, {"url": "https://github.com/tm-kn/django-basic-auth-ip-whitelist/security/advisories/GHSA-m38j-pmg3-v5x5", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://groups.google.com/forum/#%21msg/django-developers/iAaq0pvHXuA/fpUuwjK3i2wJ", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-208"}]}], "descriptions": [{"lang": "en", "value": "In django-basic-auth-ip-whitelist before 0.3.4, a potential timing attack exists on websites where the basic authentication is used or configured, i.e. BASIC_AUTH_LOGIN and BASIC_AUTH_PASSWORD is set. Currently the string comparison between configured credentials and the ones provided by users is performed through a character-by-character string comparison. This enables a possibility that attacker may time the time it takes the server to validate different usernames and password, and use this knowledge to work out the valid credentials. This attack is understood not to be realistic over the Internet. However, it may be achieved from within local networks where the website is hosted, e.g. from inside a data centre where a website's server is located. Sites protected by IP address whitelisting only are unaffected by this vulnerability. This vulnerability has been fixed on version 0.3.4 of django-basic-auth-ip-whitelist. Update to version 0.3.4 as soon as possible and change basic authentication username and password configured on a Django project using this package. A workaround without upgrading to version 0.3.4 is to stop using basic authentication and use the IP whitelisting component only. It can be achieved by not setting BASIC_AUTH_LOGIN and BASIC_AUTH_PASSWORD in Django project settings."}, {"lang": "es", "value": "En django-basic-auth-ip-whitelist versiones anteriores a 0.3.4, se presenta un posible ataque de sincronizaci\u00f3n en los sitios web donde es usada o configurada la autenticaci\u00f3n b\u00e1sica, es decir, es configurada BASIC_AUTH_LOGIN y BASIC_AUTH_PASSWORD. Actualmente, la comparaci\u00f3n de cadenas entre las credenciales configuradas y las proporcionadas por los usuarios es llevada a cabo por medio de una comparaci\u00f3n de cadena car\u00e1cter por car\u00e1cter. Esto permite una posibilidad de que un atacante tome el tiempo que le toma al servidor para comprobar diferentes nombres de usuario y contrase\u00f1as, y usar este conocimiento para obtener las credenciales validas. Se entiende que este ataque no es realista en Internet. Sin embargo, puede lograrse desde las redes locales donde est\u00e1 alojado el sitio web, por ejemplo desde el interior de un centro de datos donde est\u00e1 ubicado el servidor de un sitio web. Los sitios protegidos por la lista blanca de direcciones IP no solo est\u00e1n afectados por esta vulnerabilidad. Esta vulnerabilidad ha sido corregida en la versi\u00f3n 0.3.4 de django-basic-auth-ip-whitelist. Actualice a la versi\u00f3n 0.3.4 lo antes posible y cambie el nombre de usuario y la contrase\u00f1a de autenticaci\u00f3n b\u00e1sica configurados en un proyecto de Django con este paquete. Una soluci\u00f3n alternativa sin actualizar a la versi\u00f3n 0.3.4 es dejar de usar la autenticaci\u00f3n b\u00e1sica y usar solo el componente IP whitelisting. Se puede lograr al no configurar BASIC_AUTH_LOGIN y BASIC_AUTH_PASSWORD en la configuraci\u00f3n del proyecto Django"}], "lastModified": "2024-11-21T05:32:15.157", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:django-basic-auth-ip-whitelist_project:django-basic-auth-ip-whitelist:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "556C6FB5-D371-4726-868D-8D26D530AFEE", "versionEndExcluding": "0.3.4"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}