Skip to content

Product

crates.io gitoxide vulnerabilities

9 published CVES affecting crates.io gitoxide, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
9
Critical
0
High
4
Medium
4
Low
1
Unscored
0
CISA KEV
0

Latest crates.io gitoxide CVEs

Newest publication first

  1. HighCVSS 8.7 EPSS 0.52%

    gitoxide before 0.52.1 fails to validate submodule names from .gitmodules configuration, allowing path traversal when deriving submodule git directories. Attackers can craft malicious submodule names with traversal segments to redirect state() and open() functions to repositories...

  2. MediumCVSS 6.8 EPSS 0.26%

    gitoxide is an implementation of git written in Rust. Before 0.42.0, gitoxide uses SHA-1 hash implementations without any collision detection, leaving it vulnerable to hash collision attacks. gitoxide uses the sha1_smol or sha1 crate, both of which implement standard SHA-1 withou...

  3. LowCVSS 2.5 EPSS 0.20%

    gitoxide An idiomatic, lean, fast & safe pure Rust implementation of Git. gitoxide-core, which provides most underlying functionality of the gix and ein commands, does not neutralize newlines, backspaces, or control characters—including those that form ANSI escape sequences—that...

  4. MediumCVSS 6.4 EPSS 0.51%

    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 i...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.