Vulnerability 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 Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Django-User-Sessions Project | Django-User-Sessions | < 1.7.1 |
Related Weaknesses (CWE)
References
- https://github.com/Bouke/django-user-sessions/security/advisories/GHSA-5fq8-3q2fThird Party Advisory
- https://github.com/jazzband/django-user-sessions/commit/f0c4077e7d1436ba6d721af8Patch
- https://github.com/Bouke/django-user-sessions/security/advisories/GHSA-5fq8-3q2fThird Party Advisory
- https://github.com/jazzband/django-user-sessions/commit/f0c4077e7d1436ba6d721af8Patch
FAQ
What is CVE-2020-5224?
CVE-2020-5224 is a vulnerability with a CVSS score of 6.5 (MEDIUM). 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 rende...
How severe is CVE-2020-5224?
CVE-2020-5224 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2020-5224?
Check the references section above for vendor advisories and patch information. Affected products include: Django-User-Sessions Project Django-User-Sessions.