Approved changes feed: RSS · Atom
cpe:2.3:a:sparklemotion:mechanize:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Sparklemotion (9afae122-2fa2-5d57-8112-a64227088e04) |
|---|---|
| Product | Mechanize (9a947821-4425-5d9a-942b-e98481ee6902) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-107399 |
vulnerable | 2026-11-03 10:15:59.397292 |
Mechanize sends credential headers to another origin after a meta refresh
MEDIUM (6.8)
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.
Published: 2026-10-08T21:24:46.349Z
Updated: 2026-10-14T01:21:37.665Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-31033 |
vulnerable | 2026-06-08 05:43:40.024012 |
Authorization header leak in rubygem Mechanize
MEDIUM (5.9)
The Mechanize library is used for automating interaction with websites. Mechanize automatically stores and sends cookies, follows redirects, and can follow links and submit forms. In versions prior to 2.8.5 the Authorization header is leaked after a redirect to a different port on the same site. Users are advised to upgrade to Mechanize v2.8.5 or later. There are no known workarounds for this issue.
Published: 2022-06-09T20:00:16.000Z
Updated: 2025-04-23T18:17:26.066Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21289 |
vulnerable | 2026-06-08 05:29:11.518993 |
Command Injection Vulnerability in Mechanize
HIGH (7.4)
Mechanize is an open-source ruby library that makes automated web interaction easy. In Mechanize from version 2.0.0 and before version 2.7.7 there is a command injection vulnerability. Affected versions of mechanize allow for OS commands to be injected using several classes' methods which implicitly use Ruby's Kernel.open method. Exploitation is possible only if untrusted input is used as a local filename and passed to any of these calls: Mechanize::CookieJar#load, Mechanize::CookieJar#save_as, Mechanize#download, Mechanize::Download#save, Mechanize::File#save, and Mechanize::FileResponse#read_body. This is fixed in version 2.7.7.
Published: 2021-02-02T18:50:13.000Z
Updated: 2024-08-03T18:09:15.157Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.