PYSEC-2021-113
Vulnerability from pysec - Published: 2021-02-22 03:15 - Updated: 2021-02-26 12:36Django 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.
| Name | purl | channels | pkg:pypi/channels |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "channels",
"purl": "pkg:pypi/channels"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.0.3"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.0.0",
"3.0.1",
"3.0.2"
]
}
],
"aliases": [
"CVE-2020-35681",
"GHSA-v542-8q9x-cffc"
],
"details": "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\u0027s similar ASGIHandler, available from Django 3.0.",
"id": "PYSEC-2021-113",
"modified": "2021-02-26T12:36:00Z",
"published": "2021-02-22T03:15:00Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/django/channels/releases"
},
{
"type": "WEB",
"url": "https://channels.readthedocs.io/en/stable/releases/3.0.3.html"
},
{
"type": "WEB",
"url": "https://channels.readthedocs.io/en/stable/releases/index.html"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-v542-8q9x-cffc"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.