{"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-5145 in the wild and no public exploit code.","fix":"Upgrade django to 1.8.3 or later.","what":"CVE-2015-5145 is a high-severity denial of service vulnerability in Djangoproject Django, published on 14 Jul 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-5145 and fix it if it is affected.\n\nWhat it is: CVE-2015-5145 is a high-severity denial of service vulnerability in Djangoproject Django, published on 14 Jul 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-5145 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.3\n- django (PyPI): affected from 1.8a1; fixed in 1.8.3\n- Django (PyPI): affected from 1.8a1; fixed in 1.8.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-2015-5145/ (Markdown: https://insights.sbomify.com/CVE-2015-5145/index.md)","id":"CVE-2015-5145","markdown":"https://insights.sbomify.com/CVE-2015-5145/index.md","name":"CVE-2015-5145","record":{"aliases":["GHSA-cqf7-ff9h-7967","PYSEC-2015-21"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Django web framework","requires_auth":"none","summary":"Remote attackers can cause denial of service via CPU consumption in Django's URL validator, affecting web applications using the library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django","vendor":"djangoproject"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:C","version":"2.0"},"cwes":[{"id":"CWE-399","name":null}],"description":"validators.URLValidator in Django 1.8.x before 1.8.3 allows remote attackers to cause a denial of service (CPU consumption) via unspecified vectors.","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 ReDoS in validators.URLValidator","id":"CVE-2015-5145","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"djangoproject:django","products":["djangoproject:django"],"type":"denial_of_service","year":"2015"},"n_packages":3,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2015-5146"},"packages":[{"ecosystem":"PyPI","fixed":["1.8.3"],"introduced":["1.8a1"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-cqf7-ff9h-7967"},{"ecosystem":"PyPI","fixed":["1.8.3"],"introduced":["1.8"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2015-21"},{"ecosystem":"PyPI","fixed":["1.8.3"],"introduced":["1.8a1"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-cqf7-ff9h-7967"}],"prev":{"headline":"Django Vulnerable to HTTP Response Splitting Attack","id":"CVE-2015-5144"},"products":["n/a"],"published":"2015-07-14","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":"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 cause denial of service via CPU consumption in Django's URL validator, affecting web applications using the library.","url":"https://insights.sbomify.com/CVE-2015-5145/"}