{"answers":{"affected":"3 open source packages ship an affected version, including scrapy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-14158 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-14158 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-14158 is a high-severity denial of service vulnerability in n/a, published on 5 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-14158 and fix it if it is affected.\n\nWhat it is: CVE-2017-14158 is a high-severity denial of service vulnerability in n/a, published on 5 Sep 2017. 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-2017-14158 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- scrapy (PyPI): affected from 0.7; no fix listed\n- scrapy (PyPI): affected from 0.7 up to 2.15.2; no fix listed\n- scrapy (PyPI): affected from 0.7 up to 2.15.2; no fix listed\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-2017-14158/ (Markdown: https://insights.sbomify.com/CVE-2017-14158/index.md)","id":"CVE-2017-14158","markdown":"https://insights.sbomify.com/CVE-2017-14158/index.md","name":"CVE-2017-14158","record":{"aliases":["DEBIAN-CVE-2017-14158","GHSA-h7wm-ph43-c39p","PYSEC-2017-83","UBUNTU-CVE-2017-14158"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python web scraping library","requires_auth":"none","summary":"Remote attackers can cause denial of service in Scrapy by uploading large files that exhaust memory during processing.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"scrapy","vendor":"scrapy"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Scrapy 1.4 allows remote attackers to cause a denial of service (memory consumption) via large files because arbitrarily many files are read into memory, which is especially problematic if the files are then individually written in a separate thread to a slow storage resource, as demonstrated by interaction between dataReceived (in core/downloader/handlers/http11.py) and S3FilesStore.","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":false,"headline":"Scrapy denial of service vulnerability","id":"CVE-2017-14158","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2017"},"n_packages":3,"n_references":2,"next":{"headline":"Race condition in n/a","id":"CVE-2017-14159"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0.7"],"last_affected":[],"package":"scrapy","purl":"pkg:pypi/scrapy","source":"PYSEC-2017-83"},{"ecosystem":"PyPI","fixed":[],"introduced":["0.7"],"last_affected":["2.15.2"],"package":"scrapy","purl":null,"source":"GHSA-h7wm-ph43-c39p"},{"ecosystem":"PyPI","fixed":[],"introduced":["0.7"],"last_affected":["2.15.2"],"package":"scrapy","purl":"pkg:pypi/scrapy","source":"GHSA-h7wm-ph43-c39p"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2017-14156"},"products":["n/a"],"published":"2017-09-05","related":[{"cvss_score":7.5,"headline":"Authorization Header Leakage in scrapy/scrapy on Scheme Change Redirects","id":"CVE-2024-1968","kev_date_added":null,"published":"2024-05-20"},{"cvss_score":7.5,"headline":"XML External Entity (XXE) Vulnerability in scrapy/scrapy","id":"CVE-2024-3572","kev_date_added":null,"published":"2024-04-16"},{"cvss_score":7.5,"headline":"Authorization Header Leak During Cross-Domain Redirect in scrapy/scrapy","id":"CVE-2024-3574","kev_date_added":null,"published":"2024-04-16"},{"cvss_score":7.5,"headline":"ReDoS Vulnerability in scrapy/scrapy's XMLFeedSpider","id":"CVE-2024-1892","kev_date_added":null,"published":"2024-02-28"}],"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-05","vendors":["n/a"]},"summary":"Remote attackers can cause denial of service in Scrapy by uploading large files that exhaust memory during processing.","url":"https://insights.sbomify.com/CVE-2017-14158/"}