From upstream : CVE-2015-3982 - Fixed session flushing in the cached_db backend A change to session.flush() in the cached_db session backend in Django 1.8 mistakenly sets the session key to an empty string rather than None. An empty string is treated as a valid session key and the session cookie is set accordingly. Any users with an empty string in their session cookie will use the same session store. session.flush() is called by django.contrib.auth.logout() and, more seriously, by django.contrib.auth.login() when a user switches accounts. If a user is logged in and logs in again to a different account (without logging out) the session is flushed to avoid reuse. After the session is flushed (and its session key becomes '') the account details are set on the session and the session is saved. Any users with an empty string in their session cookie will now be logged into that account. This is fixed in 1.8.2, Django 1.7 and older are not affected.
URL: (none) => https://www.djangoproject.com/weblog/2015/may/20/security-release/CVE: (none) => CVE-2015-3982Source RPM: (none) => python-django-1.8-1.mga5
Built fine locally, freeze push requested.
CC: (none) => luigiwalser
python-django-1.8.2-1.mga5 uploaded for Cauldron. Thanks for the report!
Status: NEW => RESOLVEDResolution: (none) => FIXED
Upstream reference: https://www.djangoproject.com/weblog/2015/may/20/security-release/ Fedora has issued an advisory for this on May 22: https://lists.fedoraproject.org/pipermail/package-announce/2015-May/159156.html
URL: https://www.djangoproject.com/weblog/2015/may/20/security-release/ => http://lwn.net/Vulnerabilities/646893/