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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published: 2021-02-22T02:03:14

Updated: 2024-08-04T17:09:14.591Z

Reserved: 2020-12-24T00:00:00

Link: CVE-2020-35681

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2021-02-22T03:15:14.310

Modified: 2024-11-21T05:27:50.150

Link: CVE-2020-35681

cve-icon Redhat

Severity : Moderate

Publid Date: 2020-12-28T00:00:00Z

Links: CVE-2020-35681 - Bugzilla