CVE-2020-35681

{"id": "CVE-2020-35681", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 5.8, "accessVector": "NETWORK", "vectorString": "AV:N/AC:M/Au:N/C:P/I:N/A:P", "authentication": "NONE", "integrityImpact": "NONE", "accessComplexity": "MEDIUM", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 4.9, "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": 7.4, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 2.2}]}, "published": "2021-02-22T03:15:14.310", "references": [{"url": "https://channels.readthedocs.io/en/stable/releases/3.0.3.html", "tags": ["Exploit", "Vendor Advisory"], "source": "cve@mitre.org"}, {"url": "https://channels.readthedocs.io/en/stable/releases/index.html", "tags": ["Release Notes", "Vendor Advisory"], "source": "cve@mitre.org"}, {"url": "https://github.com/django/channels/releases", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-200"}]}], "descriptions": [{"lang": "en", "value": "Django Channels 3.x before 3.0.3 allows remote attackers to obtain sensitive information from a different request scope. The legacy channels.http.AsgiHandler class, used for handling HTTP type requests in an ASGI environment prior to Django 3.0, did not correctly separate request scopes in Channels 3.0. In many cases this would result in a crash but, with correct timing, responses could be sent to the wrong client, resulting in potential leakage of session identifiers and other sensitive data. Note that this affects only the legacy Channels provided class, and not Django's similar ASGIHandler, available from Django 3.0."}, {"lang": "es", "value": "Django Channels versiones 3.x anteriores a 3.0.3, permite a atacantes remotos obtener informaci\u00f3n confidencial de un alcance de petici\u00f3n diferente. La clase channels.http.AsgiHandler legacy, usada para manejar peticiones de tipo HTTP en un entorno ASGI anterior a Django versi\u00f3n 3.0, no separaba correctamente los \u00e1mbitos de petici\u00f3n en Channels versi\u00f3n 3.0. En muchos casos, esto resulta en un bloqueo, pero, con el tiempo correcto, las respuestas podr\u00edan ser enviadas al cliente equivocado, resultando en una posible filtraci\u00f3n de identificadores de sesi\u00f3n y otros datos confidenciales. Note que esto afecta solo a la clase legacy proporcionada de Channels, y no al ASGIHandler similar de Django, disponible en Django versi\u00f3n 3.0"}], "lastModified": "2021-02-26T12:36:23.347", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:djangoproject:channels:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "C5482767-E2F1-4DBB-ABA0-784105F6D861", "versionEndExcluding": "3.0.3", "versionStartIncluding": "3.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "cve@mitre.org"}