CVE-2020-5224 Session key exposure through session list in Django User Sessions
Attackers can steal session keys from rendered HTML if an XSS vulnerability exists, leading to account takeover in Django applications using this library.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2020-5224?
CVE-2020-5224 is a medium-severity vulnerability in Jazzband django-user-sessions, published on 24 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official 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.
Which versions are affected by CVE-2020-5224?
3 open source packages ship an affected version, including django-user-sessions. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
django-user-sessions PyPI | All versions | 1.7.1 |
django-user-sessions PyPI | All versions | 1.7.1 |
django-user-sessions PyPI | All versions | 1.7.1 |
Products include Django-User-Sessions Project Django-User-Sessions.
How do I fix CVE-2020-5224?
Upgrade django-user-sessions to 1.7.1 or later.
Is CVE-2020-5224 being exploited?
There is no known exploitation of CVE-2020-5224 in the wild and no public exploit code.
Sources
Also known as GHSA-5fq8-3q2f-4m5g, PYSEC-2020-230.