GHSA-v542-8q9x-cffc

Suggest an improvement
Source
https://github.com/advisories/GHSA-v542-8q9x-cffc
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/03/GHSA-v542-8q9x-cffc/GHSA-v542-8q9x-cffc.json
JSON Data
https://api.test.osv.dev/v1/vulns/GHSA-v542-8q9x-cffc
Aliases
Published
2021-03-19T21:29:02Z
Modified
2024-09-13T18:02:51.431471Z
Severity
  • 7.4 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H CVSS Calculator
  • 8.2 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CVSS Calculator
Summary
Django Channels leakage of session identifiers using legacy AsgiHandler
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's similar ASGIHandler, available from Django 3.0.

Database specific
{
    "nvd_published_at": "2021-02-22T03:15:00Z",
    "cwe_ids": [
        "CWE-200"
    ],
    "severity": "HIGH",
    "github_reviewed": true,
    "github_reviewed_at": "2021-03-13T00:47:11Z"
}
References

Affected packages

PyPI / channels

Package

Affected ranges

Type
ECOSYSTEM
Events
Introduced
3.0.0
Fixed
3.0.3

Affected versions

3.*

3.0.0
3.0.1
3.0.2