gix-transport indirect code execution via malicious username
Byron gitoxide
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| gix-transport crates.io |
|
|
| gix crates.io |
|
|
| gitoxide |
Byron gitoxide
| Product | Affected | Fixed in |
|---|---|---|
| gix-transport crates.io |
|
|
| gix crates.io |
|
|
| gitoxide |
|
|
gitoxide is a pure Rust implementation of Git. `gix-transport` does not check the username part of a URL for text that the external `ssh` program would interpret as an option. A specially crafted clone URL can smuggle options to SSH. The possibilities are syntactically limited, but if a malicious clone URL is used by an application whose current working directory contains a malicious file, arbitrary code execution occurs. This is related to the patched vulnerability GHSA-rrjw-j4m2-mf34, but appears less severe due to a greater attack complexity. This issue has been patched in versions 0.35.0, 0.42.0 and 0.62.0.
From the CVE record · GitHub_M
gix-transport does not check whether the username in a clone URL will be interpreted as an option by the external SSH program. If an application uses a malicious clone URL while its current working directory contains a malicious file, an attacker can achieve arbitrary code execution.
Check applications using crates.io packages gix-transport before 0.42.0, gix before 0.62.0, or gitoxide before 0.35.0.