CVE-2020-5224
In Django User Sessions (django-user-sessions) before 1.7.1, the views provided allow users to terminate specific sessions.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.53%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
In Django User Sessions (django-user-sessions) before 1.7.1, the views provided allow users to terminate specific sessions. The session key is used to identify sessions, and thus included in the rendered HTML. In itself this is not a problem. However if the website has an XSS vulnerability, the session key could be extracted by the attacker and a session takeover could happen.
- CVSS 3.1
- 8.8 HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 0.53% probability · 43th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-287, CWE-326
- Affected
- django-user-sessions project/django-user-sessions
- Source
- security-advisories@github.com
References
- https://github.com/Bouke/django-user-sessions/security/advisories/GHSA-5fq8-3q2f-4m5gThird Party Advisory
- https://github.com/jazzband/django-user-sessions/commit/f0c4077e7d1436ba6d721af85cee89222ca5d2d9Patch
- https://github.com/Bouke/django-user-sessions/security/advisories/GHSA-5fq8-3q2f-4m5gThird Party Advisory
- https://github.com/jazzband/django-user-sessions/commit/f0c4077e7d1436ba6d721af85cee89222ca5d2d9Patch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.