Where
-Infinity
0
Severity
7.4
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Problem

Scrapy’s S3DownloadHandler sends signed S3 requests over plaintext HTTP by default.

A normal request like s3://bucket/key is converted into http://bucket.s3.amazonaws.com/key unless request.meta["issecure"] is explicitly set. The generated request is then signed with configured AWS credentials, so AWS authorization material can be sent without TLS.

Vulnerable code in scrapy/core/downloader/handlers/s3.py:

python scheme = "https" if request.meta.get("issecure") else "http" url = f"{scheme}://{bucket}.s3.amazonaws.com{path}"

The request is then signed and dispatched:

python self.signer.addauth(awsrequest) request = request.replace(url=url, headers=awsrequest.headers.items())

Impact

Users making Scrapy s3:// requests with AWS credentials are impacted.

A network attacker able to observe traffic between Scrapy and S3, such as a public Wi-Fi attacker, compromised router, ISP/corporate network observer, or local network attacker using ARP spoofing, can read:

text bucket/key path AWS Authorization header X-Amz-Security-Token, if temporary credentials are used S3 object contents S3 response headers

An active MITM attacker can also modify the plaintext S3 response body, status code, and headers before Scrapy processes it. This can cause scraped data poisoning, poisoned exports, HTTP cache poisoning when cache is enabled, and influence over later crawl targets through forged redirects or attacker-controlled links.

Suggested classification: CWE-319: Cleartext Transmission of Sensitive Information.

PoC

A minimal PoC creates an s3:// request, enables fake AWS settings, captures the request produced by S3DownloadHandler, and prints the rewritten URL and auth headers.

1 / 2
Source: GitHub
First published (updated )
Severity
7.8
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

First published (updated )

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