🛡️ CVE-2015-3982 — django

⚪ Unknown ✅ No Known Exploit CWE-384 OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Django allows user sessions hijacking via an empty string in the session key

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.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. Rated impact: confidentiality none, integrity high, availability none.

Weakness class

CVE-2015-3982 is classified as CWE-384: Session Fixation. A session identifier is not renewed at login, so an identifier planted beforehand becomes an authenticated session.

Affected software

CVE-2015-3982 is recorded against 1 package.

  • django (from 1.8a1 up to 1.8.2)

Timeline and source

Published on 17 May 2022 and last revised on 17 September 2024. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

nvd.nist.gov (Advisory)
github.com (Web)
github.com (Package)
github.com (Web)
web.archive.org (Web)
www.djangoproject.com (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U
CWE CWE-384
Public Exploit ✅ No
Source OSV
Published 2022-05-17
Updated 2026-08-12
Modified 2024-09-17
Fix URL N/A

Affected Packages

Software From version Fixed in
django 1.8a1 1.8.2

Free Vulnerability Check

Is your site affected by CVE-2015-3982?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2015-3982 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.