{"answers":{"affected":"7 open source packages ship an affected version, including django and Django. It affects 2 products.","exploited":"There is no known exploitation of CVE-2014-0473 in the wild and no public exploit code.","fix":"Upgrade django to a fixed version for your release line: 1.4.11, 1.5.6 or 1.6.3.","what":"CVE-2014-0473 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 23 Apr 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2014-0473 and fix it if it is affected.\n\nWhat it is: CVE-2014-0473 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 23 Apr 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2014-0473 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django (PyPI): affected all versions; fixed in 1.4.11, 1.5.6, 1.6.3\n- django (PyPI): affected all versions; fixed in 1.4.11\n- django (PyPI): affected from 1.5; fixed in 1.5.6\n- django (PyPI): affected from 1.6; fixed in 1.6.3\n- Django (PyPI): affected all versions; fixed in 1.4.11\n- Django (PyPI): affected from 1.5; fixed in 1.5.6\n- Django (PyPI): affected from 1.6; fixed in 1.6.3\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-2014-0473/ (Markdown: https://insights.sbomify.com/CVE-2014-0473/index.md)","id":"CVE-2014-0473","markdown":"https://insights.sbomify.com/CVE-2014-0473/index.md","name":"CVE-2014-0473","record":{"aliases":["DEBIAN-CVE-2014-0473","GHSA-89hj-xfx5-7q66","PYSEC-2014-2","UBUNTU-CVE-2014-0473"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Django web framework","requires_auth":"none","summary":"Remote attackers can bypass CSRF protections by reusing cached tokens for anonymous users, requiring user interaction to exploit.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"debian","cpe":[{"product":"ubuntu_linux","vendor":"canonical"},{"product":"django","vendor":"djangoproject"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"The caching framework in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 reuses a cached CSRF token for all anonymous users, which allows remote attackers to bypass CSRF protections by reading the CSRF cookie for anonymous users.","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 Reuses Cached CSRF Token","id":"CVE-2014-0473","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"canonical:ubuntu_linux","products":["canonical:ubuntu_linux","djangoproject:django"],"type":"csrf","year":"2014"},"n_packages":7,"n_references":7,"next":{"headline":"Django Vulnerable to MySQL Injection","id":"CVE-2014-0474"},"packages":[{"ecosystem":"PyPI","fixed":["1.4.11"],"introduced":["0"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-89hj-xfx5-7q66"},{"ecosystem":"PyPI","fixed":["1.5.6"],"introduced":["1.5"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-89hj-xfx5-7q66"},{"ecosystem":"PyPI","fixed":["1.6.3"],"introduced":["1.6"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-89hj-xfx5-7q66"},{"ecosystem":"PyPI","fixed":["1.4.11","1.5.6","1.6.3"],"introduced":["0","1.5","1.6"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2014-2"},{"ecosystem":"PyPI","fixed":["1.4.11"],"introduced":["0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-89hj-xfx5-7q66"},{"ecosystem":"PyPI","fixed":["1.5.6"],"introduced":["1.5"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-89hj-xfx5-7q66"},{"ecosystem":"PyPI","fixed":["1.6.3"],"introduced":["1.6"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-89hj-xfx5-7q66"}],"prev":{"headline":"Code Injection in Django","id":"CVE-2014-0472"},"products":["n/a"],"published":"2014-04-23","related":[{"cvss_score":9.8,"headline":"SaltStack Salt Authentication Bypass","id":"CVE-2020-11651","kev_date_added":"2021-11-03","published":"2020-04-30"},{"cvss_score":9.8,"headline":"OpenSMTPD Remote Code Execution","id":"CVE-2020-7247","kev_date_added":"2022-03-25","published":"2020-01-29"},{"cvss_score":9.8,"headline":"Exim Out-of-bounds Write","id":"CVE-2019-16928","kev_date_added":"2022-03-03","published":"2019-09-27"},{"cvss_score":9.8,"headline":"Exim Buffer Overflow","id":"CVE-2018-6789","kev_date_added":"2021-11-03","published":"2018-02-08"},{"cvss_score":9.8,"headline":"Oracle Java SE and Java SE Embedded Remote Code Execution","id":"CVE-2015-2590","kev_date_added":"2022-03-03","published":"2015-07-16"},{"cvss_score":9.8,"headline":"Oracle JRE Remote Code Execution","id":"CVE-2013-0422","kev_date_added":"2022-05-25","published":"2013-01-10"},{"cvss_score":9.8,"headline":"Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution","id":"CVE-2011-3544","kev_date_added":"2022-03-03","published":"2011-10-19"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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 bypass CSRF protections by reusing cached tokens for anonymous users, requiring user interaction to exploit.","url":"https://insights.sbomify.com/CVE-2014-0473/"}