First published: Mon Feb 22 2021(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Channels | >=3.0.0<3.0.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-35681 is a vulnerability in Django Channels 3.x before 3.0.3 that allows remote attackers to obtain sensitive information from a different request scope.
CVE-2020-35681 has a severity rating of 7.4 (high).
CVE-2020-35681 affects Django Channels 3.x versions before 3.0.3 as well as the Djangoproject Channels package.
To fix CVE-2020-35681, upgrade to Django Channels 3.0.3 or later.
More information about CVE-2020-35681 can be found at the NVD (National Vulnerability Database) and the official Django Channels documentation.