Django up to 3.0.2 ASGI channels.http.AsgiHandler information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Django up to 3.0.2. The impacted element is the function channels.http.AsgiHandler of the component ASGI Handler. This manipulation causes an unknown weakness.
This vulnerability is handled as CVE-2020-35681. The attack can be initiated remotely. There is not any exploit available.
You should upgrade the affected component.
Details
A vulnerability has been found in Django up to 3.0.2 (Content Management System) and classified as critical. Affected by this vulnerability is the function channels.http.AsgiHandler of the component ASGI Handler. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was released 02/22/2021. The advisory is shared at channels.readthedocs.io. This vulnerability is known as CVE-2020-35681. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 3.0.3 eliminates this vulnerability. The upgrade is hosted for download at channels.readthedocs.io.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.4
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Django 3.0.3
Timeline
12/24/2020 🔍02/22/2021 🔍
02/22/2021 🔍
03/03/2021 🔍
Sources
Advisory: channels.readthedocs.ioStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2020-35681 (🔍)
GCVE (CVE): GCVE-0-2020-35681
GCVE (VulDB): GCVE-100-170221
Entry
Created: 02/22/2021 09:08Updated: 03/03/2021 23:55
Changes: 02/22/2021 09:08 (39), 03/03/2021 23:48 (6), 03/03/2021 23:55 (20)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.