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 outside .git/modules, causing repository confusion and inspection of attacker-controlled repositories.

A path traversal vulnerability exists in gitoxide before version 0.52.1, stemming from insufficient validation of submodule names read from .gitmodules configuration files. Attackers can craft malicious submodule names containing directory traversal segments to redirect the state() and open() functions to repositories located outside the expected .git/modules directory. This can lead to repository confusion and allow attackers to cause inspection of attacker-controlled repositories. The vulnerability affects the core submodule handling logic of the gitoxide Rust-based Git implementation. Exploitation requires a victim to process a maliciously crafted repository containing manipulated .gitmodules entries. The fix was introduced in gitoxide version 0.52.1, which adds proper validation of submodule names before use in path derivation.