CVE-2020-35681
Django Channels 3.x before 3.0.3 allows remote attackers to obtain sensitive information from a different request scope.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (2.66%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.1
- 7.4 HIGHCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H
- EPSS
- 2.66% probability · 85th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-200
- Affected
- djangoproject/channels
- Source
- cve@mitre.org
References
- https://channels.readthedocs.io/en/stable/releases/3.0.3.htmlExploit, Vendor Advisory
- https://channels.readthedocs.io/en/stable/releases/index.htmlRelease Notes, Vendor Advisory
- https://github.com/django/channels/releasesThird Party Advisory
- https://channels.readthedocs.io/en/stable/releases/3.0.3.htmlExploit, Vendor Advisory
- https://channels.readthedocs.io/en/stable/releases/index.htmlRelease Notes, Vendor Advisory
- https://github.com/django/channels/releasesThird Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.