{"answers":{"affected":"5 open source packages ship an affected version, including django and Django. It affects 1 product.","exploited":"There is no known exploitation of CVE-2009-2659 in the wild and no public exploit code.","fix":"Upgrade django to a fixed version for your release line: 1.1, 0.96.4 or 1.0.3.","what":"CVE-2009-2659 is a medium-severity path traversal vulnerability in n/a, published on 4 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-2659 and fix it if it is affected.\n\nWhat it is: CVE-2009-2659 is a medium-severity path traversal vulnerability in n/a, published on 4 Aug 2009. 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-2009-2659 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django (PyPI): affected all versions; fixed in 1.1\n- django (PyPI): affected from 0.96.0; fixed in 0.96.4\n- django (PyPI): affected from 1.0; fixed in 1.0.3\n- Django (PyPI): affected from 0.96.0; fixed in 0.96.4\n- Django (PyPI): affected from 1.0; fixed in 1.0.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-2009-2659/ (Markdown: https://insights.sbomify.com/CVE-2009-2659/index.md)","id":"CVE-2009-2659","markdown":"https://insights.sbomify.com/CVE-2009-2659/index.md","name":"CVE-2009-2659","record":{"aliases":["DEBIAN-CVE-2009-2659","GHSA-9xg7-gg9m-rmq9","PYSEC-2009-3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Django web framework","requires_auth":"none","summary":"Remote attackers can read arbitrary files via crafted URLs in the Django Admin media handler due to improper path mapping.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django","vendor":"django_project"}],"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-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The Admin media handler in core/servers/basehttp.py in Django 1.0 and 0.96 does not properly map URL requests to expected \"static media files,\" which allows remote attackers to conduct directory traversal attacks and read arbitrary files via a crafted URL.","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 Admin Media Handler Vulnerable to Directory Traversal","id":"CVE-2009-2659","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2009"},"n_packages":5,"n_references":9,"next":{"headline":"Integer overflow in n/a","id":"CVE-2009-2660"},"packages":[{"ecosystem":"PyPI","fixed":["0.96.4"],"introduced":["0.96.0"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-9xg7-gg9m-rmq9"},{"ecosystem":"PyPI","fixed":["1.0.3"],"introduced":["1.0"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-9xg7-gg9m-rmq9"},{"ecosystem":"PyPI","fixed":["1.1"],"introduced":["0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2009-3"},{"ecosystem":"PyPI","fixed":["0.96.4"],"introduced":["0.96.0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-9xg7-gg9m-rmq9"},{"ecosystem":"PyPI","fixed":["1.0.3"],"introduced":["1.0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-9xg7-gg9m-rmq9"}],"prev":{"headline":"Path traversal in n/a","id":"CVE-2009-2658"},"products":["n/a"],"published":"2009-08-04","related":[{"cvss_score":7.5,"headline":"Django Arbitrary Code Execution","id":"CVE-2007-0404","kev_date_added":null,"published":"2007-01-23"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2007-5828","kev_date_added":null,"published":"2007-11-05"},{"cvss_score":6.5,"headline":"Django Improper Access Control","id":"CVE-2007-0405","kev_date_added":null,"published":"2007-01-23"},{"cvss_score":4.3,"headline":"Django Cross-site scripting (XSS) vulnerability","id":"CVE-2008-2302","kev_date_added":null,"published":"2008-05-23"},{"cvss_score":2.6,"headline":"Django vulnerable to Denial of Service via i18n middleware component","id":"CVE-2007-5712","kev_date_added":null,"published":"2007-10-30"}],"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-07","vendors":["n/a"]},"summary":"Remote attackers can read arbitrary files via crafted URLs in the Django Admin media handler due to improper path mapping.","url":"https://insights.sbomify.com/CVE-2009-2659/"}