CVE-2020-35681

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.

• CVE ID
• CVE-2020-35681

• Assigner
• cve@mitre.org

• Vulnerability Status
• Analyzed

• Published Version
• 2021-02-22T03:15:14

• Last Modified Date
• 2021-02-26T12:36:23

• Version
• 2.0

• Vector String
• AV:N/AC:M/Au:N/C:P/I:N/A:P

• Access Vector
• NETWORK

• Access Compatibility
• MEDIUM

• Authentication
• NONE

• Confidentiality Impact
• PARTIAL

• Integrity Impact
• NONE

• Availability Impact
• PARTIAL

• Base Score
• 5.8

• Severity
• MEDIUM

• Exploitability Score
• 8.6

• Impact Score
• 4.9

• Version
• 3.1

• Vector String
• CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H

• Attack Vector
• NETWORK

• Attack Compatibility
• HIGH

• Privileges Required
• NONE

• User Interaction
• NONE

• Scope
• UNCHANGED

• Confidentiality Impact
• HIGH

• Availability Impact
• HIGH

• Base Score
• 7.4

• Base Severity
• HIGH

• Exploitability Score
• 2.2

• Impact Score
• 5.2