Gitoxide Symlink Following .gitmodules Path Traversal

Executive Summary

gitoxide before 0.52.1 follows symlinks when reading the worktree .gitmodules file. Attackers can create a malicious repository with a symlinked .gitmodules pointing outside the repository tree. This causes gitoxide to parse arbitrary external files as submodule configuration, exposing attacker-controlled name, path, and url values.

Useful 0 Not Useful 0

Detection Guidance

Detecting this vulnerability requires checking for symlinks in .gitmodules files within git repositories using gitoxide. Inspect repositories for .gitmodules files that point outside the repository tree. Use commands like 'find . -name .gitmodules -type f -exec ls -l {} \;' to identify symlinks.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability allows attackers to inject malicious submodule metadata into your repository. This could lead to unauthorized code execution, data leaks, or supply chain attacks if you use gitoxide to process untrusted repositories.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by enabling unauthorized access to external files through symlink manipulation. Attackers may inject malicious submodule metadata, leading to exposure of sensitive configuration data outside the intended repository boundaries. This could violate data integrity and access control requirements under these regulations.

Useful 0 Not Useful 0

Mitigation Strategies

Upgrade gitoxide to version 0.52.1 or later to address the issue. Review repositories for malicious .gitmodules symlinks and remove any suspicious links. Avoid using untrusted repositories until patched.

Useful 0 Not Useful 0