The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize applies no origin trust boundary in Mechanize::HTTP::Agent#response_follow_meta_refresh when Mechanize#follow_meta_refresh is enabled. A page containing a meta refresh to another origin causes headers configured through Mechanize#request_headers= to be reapplied to the refresh request, allowing an attacker who controls content in the crawl to capture bearer tokens or session cookies.
The default configuration is not affected because follow_meta_refresh is false, and the exposure is limited to caller-supplied default headers. This issue is fixed in version 2.14.1.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
High
Difficult to exploit
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
References 5
https://github.com/sparklemotion/mechanize/commit/02a1235842d6eda8d4a5a3d8f13ab…
security-advisories@github.com
https://github.com/sparklemotion/mechanize/commit/84c74df87d15f5d119df268ba6aa7…
security-advisories@github.com
https://github.com/sparklemotion/mechanize/pull/676
security-advisories@github.com
https://github.com/sparklemotion/mechanize/releases/tag/v2.14.1
security-advisories@github.com
https://github.com/sparklemotion/mechanize/security/advisories/GHSA-c6rp-p8xm-4…
security-advisories@github.com