{"answers":{"affected":"3 open source packages ship an affected version, including django and Django. It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-3982 in the wild and no public exploit code.","fix":"Upgrade django to 1.8.2 or later.","what":"CVE-2015-3982 is a medium-severity authentication bypass vulnerability in Djangoproject Django, published on 2 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-3982 and fix it if it is affected.\n\nWhat it is: CVE-2015-3982 is a medium-severity authentication bypass vulnerability in Djangoproject Django, published on 2 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-3982 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django (PyPI): affected from 1.8; fixed in 1.8.2\n- django (PyPI): affected from 1.8a1; fixed in 1.8.2\n- Django (PyPI): affected from 1.8a1; fixed in 1.8.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2015-3982/ (Markdown: https://insights.sbomify.com/CVE-2015-3982/index.md)","id":"CVE-2015-3982","markdown":"https://insights.sbomify.com/CVE-2015-3982/index.md","name":"CVE-2015-3982","record":{"aliases":["GHSA-6wgp-fwfm-mxp3","PYSEC-2015-19"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Django web framework","requires_auth":"none","summary":"Remote attackers can hijack user sessions in Django applications using the cached_db backend by exploiting improper session flushing.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django","vendor":"djangoproject"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Django allows user sessions hijacking via an empty string in the session key","id":"CVE-2015-3982","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"djangoproject:django","products":["djangoproject:django"],"type":"auth_bypass","year":"2015"},"n_packages":3,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2015-3983"},"packages":[{"ecosystem":"PyPI","fixed":["1.8.2"],"introduced":["1.8a1"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-6wgp-fwfm-mxp3"},{"ecosystem":"PyPI","fixed":["1.8.2"],"introduced":["1.8"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2015-19"},{"ecosystem":"PyPI","fixed":["1.8.2"],"introduced":["1.8a1"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-6wgp-fwfm-mxp3"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2015-3981"},"products":["n/a"],"published":"2015-06-02","related":[{"cvss_score":9.8,"headline":"Privilege abuse in GenericInlineModelAdmin","id":"CVE-2026-4277","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.8,"headline":"Django SQL injection in HasKey(lhs, rhs) on Oracle","id":"CVE-2024-53908","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.8,"headline":"Django SQL injection vulnerability","id":"CVE-2024-42005","kev_date_added":null,"published":"2024-08-07"},{"cvss_score":9.8,"headline":"Django bypasses validation when using one form field to upload multiple files","id":"CVE-2023-31047","kev_date_added":null,"published":"2023-05-07"},{"cvss_score":9.8,"headline":"Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection","id":"CVE-2022-34265","kev_date_added":null,"published":"2022-07-04"},{"cvss_score":9.8,"headline":"SQL Injection in Django","id":"CVE-2021-35042","kev_date_added":null,"published":"2021-07-02"},{"cvss_score":9.8,"headline":"SQL injection in Django","id":"CVE-2020-7471","kev_date_added":null,"published":"2020-02-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can hijack user sessions in Django applications using the cached_db backend by exploiting improper session flushing.","url":"https://insights.sbomify.com/CVE-2015-3982/"}