Channels vulnerabilitiesRanked by how likely they are to be used.
Channels is made by Djangoproject. We track 1 published vulnerability in it, across 63 versions. None of them is on the list of flaws known to be exploited today. If you run Channels, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Channels vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Channels's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Channels flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.7%CVE-2020-35681High
Django Channels 3.x before 3.0.3 allows remote attackers to obtain sensitive information from a different request scope.
Running Channels? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Channels on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 1 published vulnerability listed under the name Channels, across 63 versions.
None of Channels's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Channels. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.