CVE-2017-14158: High severity scrapy vulnerability

Published Sep 5, 2017
·
Updated

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.

Affected Software

2 affected components
pip/scrapy>=0.7<=2.11.1
scrapy scrapy=1.4

Event History

Sep 5, 2017
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
May 17, 2022
Advisory Published
via GitHub·01:16 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-14158?

CVE-2017-14158 is categorized as a denial of service vulnerability due to memory consumption issues.

2

How do I fix CVE-2017-14158?

To remediate CVE-2017-14158, you should update Scrapy to a version that is newer than 1.4 that addresses memory management.

3

What are the potential impacts of CVE-2017-14158?

The potential impacts of CVE-2017-14158 include degraded performance and application crashes due to excessive memory consumption.

4

Which versions of Scrapy are affected by CVE-2017-14158?

CVE-2017-14158 specifically affects Scrapy version 1.4.

5

Can CVE-2017-14158 be exploited remotely?

Yes, CVE-2017-14158 can be exploited by remote attackers through the upload of large files.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203