Approved changes feed: RSS · Atom
cpe:2.3:a:djangoproject:channels:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Djangoproject (070db687-4713-5da4-80b0-4a67baf0d0d4) |
|---|---|
| Product | Channels (68c009d8-115d-5158-97db-e5b8ce910865) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/django/channels |
purl2cpe | 2026-06-01 10:17:26.954604 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-35681 |
vulnerable | 2026-06-08 05:25:01.514474 |
Details available
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.
Published: 2021-02-22T02:03:14.000Z
Updated: 2024-08-04T17:09:14.591Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.