Skip to main content
No exploitation reportedFix available

CVE-2020-35681

No exploitation reported by the sources we read.

  • Published2021-02-22
  • Fixed in3.0.3
  • WeaknessCWE-200

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2021-02-2203:15CVE publishedNVD

Versions per branch

NVD · OSV
Djangoproject channels
BranchAffectedFixed in
3.0≥ 3.0.0, < 3.0.33.0.3

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • python-django-channelsUbuntu:20.04:LTSall versions · no fixed version listed
  • python-django-channelsUbuntu:18.04:LTSall versions · no fixed version listed
  • python-django-channelsDebian:14all versions · fixed in 3.0.3-1
  • python-django-channelsDebian:13all versions · fixed in 3.0.3-1
  • python-django-channelsDebian:12all versions · fixed in 3.0.3-1

Vendor advisories

  • CVE-2020-35681 Red Hat Product Security

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

Full record on NVD

Fix

  1. Update Djangoproject channels to 3.0.3

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H
Published
2021-02-22
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-v542-8q9x-cffc

Frequently asked questions

What is CVE-2020-35681?

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.

Is CVE-2020-35681 actively exploited?

Active exploitation of CVE-2020-35681 has not been confirmed. Its EPSS score was 2.7% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-35681?

CVE-2020-35681 has a CVSS v3 base score of 7.4 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H.

Running channels? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record