Command Injection Vulnerability in Mechanize
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| sparklemotion | mechanize | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2561-1 | ruby-mechanize security update |
EUVD |
EUVD-2021-0569 | 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. |
Github GHSA |
GHSA-qrqm-fpv6-6r8g | Command Injection Vulnerability in Mechanize |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 3.5% (3.549% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.