CVE-2020-35681

django-channels: potential leakage of session identifiers using legacy AsgiHandler

Published Feb 22, 2021 CVSS 3.1 · 7.4 High EPSS 2.7% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2021-0041 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.
Github GHSA Github GHSA GHSA-v542-8q9x-cffc Django Channels leakage of session identifiers using legacy AsgiHandler
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Aug 4, 2024, 5:09 PM
Reserved
Dec 24, 2020, 12:00 AM
Status
Modified
Published
Feb 22, 2021, 3:15 AM
Modified
Jun 17, 2026, 3:14 AM
Severity
Moderate
Public date
Dec 28, 2020, 12:00 AM