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.
References
Link | Resource |
---|---|
https://channels.readthedocs.io/en/stable/releases/3.0.3.html | Exploit Vendor Advisory |
https://channels.readthedocs.io/en/stable/releases/index.html | Release Notes Vendor Advisory |
https://github.com/django/channels/releases | Third Party Advisory |
Configurations
History
No history.
Information
Published : 2021-02-22 03:15
Updated : 2024-02-28 18:08
NVD link : CVE-2020-35681
Mitre link : CVE-2020-35681
CVE.ORG link : CVE-2020-35681
JSON object : View
Products Affected
djangoproject
- channels
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor