CVE-2015-3982
What it is
The session.flush function in the cached_db backend in Django 1.8.x before 1.8.2 does not properly flush the session, which allows remote attackers to hijack user sessions via an empty string in the session key.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 1.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.8% in the next 30 days (EPSS).
- Severity: 5.0 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.8% · EPSS, next 30 days
- Record status
- Modified
Affected
- Djangoproject Django 1.8.0
- Djangoproject Django 1.8.1
Attack profile CVSS 2.0 · 5.0
- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
Raw vector
AV:N/AC:L/Au:N/C:N/I:P/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2015-3982.md and follow it. Check whether this project is affected by CVE-2015-3982. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://www.djangoproject.com/weblog/2015/may/20/security-release/
- https://www.djangoproject.com/weblog/2015/may/20/security-release/