Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

PyPI package

django-user-sessions

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.8PyPIAmendedPublished

    Session key exposure through session list in Django User Sessions

    CVE-2020-5224 · GHSA-5fq8-3q2f-4m5g

    Affected
    • PyPI django-user-sessions < 1.7.1
    Fixed in
    1.7.1· Vendor fix available
    Issue
    Impact The views provided by django-user-sessions 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. Patches Patch is under way. Workarounds Remove the sessionkey from the template. References None. For more information If you have any questions or comments about this advisory: Open an issue in Bouke/django-user-sessions Email us at bouke@haarsma.eu

    Recommended action: Upgrade to 1.7.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →