Resource exhaustion in Scrapy
CVE-2017-14158
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.
Vulnerability class: DoS (Denial of Service)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS: 0.026 (84.6th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 85th percentile — 84.6% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.027 · newest: 0.026 · change: -0.001
Affected products
- Scrapy — versions 1.4
Weakness classification (CWE)
Public proof-of-concept exploits
References
- github.com/scrapy/scrapy/issues/482 (Third Party Advisory, Issue Tracking)
- blog.csdn.net/wangtua/article/details/75228728 (Exploit, Third Party Advisory)
Frequently asked questions
- What is CVE-2017-14158?
- CVE-2017-14158 is a high-severity vulnerability in Scrapy, classified under Uncontrolled Resource Consumption. CVSS score: 7.5/10. Published 2017-09-05.
- How severe is CVE-2017-14158?
- High severity. CVSS v3 base score is 7.5 out of 10.
- Is CVE-2017-14158 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.