How severe is CVE-2015-3982?

No CVSS score has been assigned to CVE-2015-3982 yet. Review the advisory details and affected package list to assess your exposure.

Which products are affected by CVE-2015-3982?

Affected package information for CVE-2015-3982 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2015-3982?

No patch has shipped for CVE-2015-3982 yet — track the djangoproject django advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2015-3982 across my infrastructure?

Inventory every djangoproject django deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2015-3982 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2015-3982?

O3 detects and blocks CVE-2015-3982 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2015-3982 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-3982 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2015-3982?

CVE-2015-3982 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 75th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Which products and versions are affected by CVE-2015-3982?

CVE-2015-3982 affects djangoproject django (2 versions, e.g. 1.8.0, 1.8.1). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2015-3982 published, and has it been updated?

CVE-2015-3982 was published on June 2, 2015 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2015-3982: DJANGO

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk75th percentile+1.52%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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.

Affected Products

1 product · 2 configurations

Application

djangodjangoproject

2 versions

1.8.01.8.1

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every djangoproject django deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Remediation status
No patch has shipped for CVE-2015-3982 yet — track the djangoproject django advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2015-3982 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2015-3982. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Runtime Protection

Is CVE-2015-3982 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2015-3982 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2015-3982

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2015-3982 being exploited in your environment?