What is the severity of CVE-2017-14158?

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

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.

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.

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

CVE-2017-14158 specifically affects Scrapy version 1.4.

Can CVE-2017-14158 be exploited remotely?

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

Vulnerability/
CVE-2017-14158

high

7.8

CWE

400

5/9/2017

17/5/2022

5/8/2024

CVE-2017-14158

First published: Tue Sep 05 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.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
Scrapy Scrapy	=1.4
pip/scrapy	>=0.7<=2.11.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-14158?
CVE-2017-14158 is categorized as a denial of service vulnerability due to memory consumption issues.
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.
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.
Which versions of Scrapy are affected by CVE-2017-14158?
CVE-2017-14158 specifically affects Scrapy version 1.4.
Can CVE-2017-14158 be exploited remotely?
Yes, CVE-2017-14158 can be exploited by remote attackers through the upload of large files.

collector/nvd-index
agent/author
agent/type
agent/references
collector/github-advisory-latest
source/GitHub
alias/GHSA-h7wm-ph43-c39p
alias/CVE-2017-14158
agent/software-canonical-lookup
agent/severity
agent/weakness
agent/description
collector/nvd-cve
source/NVD
collector/github-advisory
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/trending
agent/tags
agent/source
vendor/scrapy
canonical/scrapy scrapy
version/scrapy scrapy/1.4
package-manager/pip

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2017-14158?
CVE-2017-14158 is categorized as a denial of service vulnerability due to memory consumption issues.
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.
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.
Which versions of Scrapy are affected by CVE-2017-14158?
CVE-2017-14158 specifically affects Scrapy version 1.4.
Can CVE-2017-14158 be exploited remotely?
Yes, CVE-2017-14158 can be exploited by remote attackers through the upload of large files.