CVEvulnerability
CVE-2020-35681
7.4 HIGH
Official page ↗
- Status
- Modified
- Published
- 2021-02-22
- Last modified
- 2026-06-17
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 7.4 HIGH — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H
- CVSS 2.0 ([email protected])
- 5.8 MEDIUM — AV:N/AC:M/Au:N/C:P/I:N/A:P
- Weaknesses
- CWE-200
Description
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.
Affected configurations
• djangoproject channels (>= 3.0.0 < 3.0.3)
Related
Weakness · CWE (1)
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor weakness
References
- 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
- 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