Path Traversal in Gitoxide via Malicious Submodule Names

Executive Summary

gitoxide before 0.52.1 does not validate submodule names from .gitmodules, enabling path traversal. Attackers can use traversal segments in submodule names to redirect functions like state() and open() to repositories outside .git/modules. This causes repository confusion and allows inspection of attacker-controlled repositories.

Useful 0 Not Useful 0

Detection Guidance

To detect this vulnerability, inspect .gitmodules files for submodule names containing path traversal sequences like '../' or '..\'. Check gitoxide versions before 0.52.1. Use commands like 'find / -name .gitmodules -type f 2>/dev/null' to locate files and 'gitoxide --version' to check versions.

Useful 0 Not Useful 0

Impact Analysis

An attacker could trick you into interacting with a malicious repository, potentially leading to unauthorized access to sensitive data, code execution, or repository corruption. This affects users relying on gitoxide for repository management.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could lead to unauthorized data exposure or code execution, violating confidentiality requirements in GDPR and HIPAA. Compliance may be impacted if sensitive data is accessed or modified without authorization.

Useful 0 Not Useful 0

Mitigation Strategies

Upgrade gitoxide to version 0.52.1 or later. Review all .gitmodules files for malicious submodule names and remove any with path traversal sequences. Audit repositories for unauthorized submodule additions.

Useful 0 Not Useful 0