Skip to content

Splash authentication credentials potentially leaked to target websites

High severity GitHub Reviewed Published Oct 5, 2021 in scrapy-plugins/scrapy-splash • Updated Feb 1, 2023

Package

pip scrapy-splash (pip)

Affected versions

< 0.8.0

Patched versions

0.8.0

Description

Impact

If you use HttpAuthMiddleware (i.e. the http_user and http_pass spider attributes) for Splash authentication, any non-Splash request will expose your credentials to the request target. This includes robots.txt requests sent by Scrapy when the ROBOTSTXT_OBEY setting is set to True.

Patches

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.

Workarounds

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.

For more information

If you have any questions or comments about this advisory:

References

@Gallaecio Gallaecio published to scrapy-plugins/scrapy-splash Oct 5, 2021
Reviewed Oct 5, 2021
Published by the National Vulnerability Database Oct 5, 2021
Published to the GitHub Advisory Database Oct 6, 2021
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

EPSS score

0.149%
(52nd percentile)

Weaknesses

CVE ID

CVE-2021-41124

GHSA ID

GHSA-823f-cwm9-4g74
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.