Splash authentication credentials potentially leaked to target websites in scrapy-splash
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.8.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Scrapy-splash is a library which provides Scrapy and JavaScript integration. In affected versions users who use `HttpAuthMiddleware` (i.e. the `http_user` and `http_pass` spider attributes) for Splash authentication will have any non-Splash request expose your credentials to the request target. This includes `robots.txt` requests sent by Scrapy when the `ROBOTSTXT_OBEY` setting is set to `True`. Upgrade to scrapy-splash 0.8.0 and use the new `SPLASH_USER` and `SPLASH_PASS` settings instead to set your Splash authentication credentials safely. If you cannot upgrade, set your Splash request credentials on a per-request basis, using the `splash_headers` request parameter, instead of defining them globally using the `HttpAuthMiddleware`. Alternatively, make sure all your requests go through Splash. That includes disabling the robots.txt middleware.
Timeline
- CVE published
- Record last updated
Affected versions
- scrapy-plugins scrapy-splash
fixed in 0.8.0
- scrapy-splashPyPI
fixed in 0.8.0