Mechanize sends credential headers to another host after an HTTP redirect
sparklemotion mechanize
sparklemotion mechanize
| Product | Affected | Fixed in |
|---|---|---|
| mechanize RubyGems |
|
|
The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize sends caller-supplied credential headers to a different host after an HTTP redirect. Mechanize#request_headers= is reapplied by Mechanize::HTTP::Agent#request_add_headers even after Mechanize::HTTP::Agent#response_redirect strips per-request headers, and the protected header lists omit Proxy-Authorization and Cookie2. An attacker who controls a redirect target can capture bearer tokens or session cookies supplied through request_headers= or the per-request headers argument, while Mechanize#cookie_jar and Mechanize::HTTP::AuthStore are not affected. This issue is fixed in version 2.14.1.
From the CVE record · GitHub_M
Mechanize versions before 2.14.1 can forward caller-supplied credential headers to a different host after an HTTP redirect. An attacker who controls the redirect target can capture bearer tokens or session cookies supplied through request_headers= or per-request headers. Mechanize’s cookie jar and AuthStore are not affected.
Anyone running the RubyGems mechanize package before version 2.14.1 should check their installation.