CyberRota Analysis
AI-GeneratedVersions 1.1.7 and earlier of GitHacker are vulnerable due to improper validation of path segments in the add_head_file_tasks function, allowing attackers to craft requests that read arbitrary local files on the victim's system. This vulnerability can lead to the disclosure of sensitive data through the exposure of hexadecimal fragments, although complete file contents are not revealed. Organizations using affected versions should prioritize upgrading to version 1.1.9 to mitigate potential data leakage risks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
GitHacker is a tool that restores Git repositories from exposed .git directories. In 1.1.7 and earlier, add_head_file_tasks parses an attacker-controlled ref path from .git/HEAD and joins unvalidated path segments onto temp_dst/.git/logs/, allowing a malicious server to make GitHacker read an arbitrary local file when a victim runs the tool against the server's URL. add_hashes_parsed then scans the file for 40-character hexadecimal substrings and requests each match through .git/objects using the first two characters and remaining characters as path components, creating an attacker-observable existence oracle and disclosing matching hexadecimal fragments. Complete file contents are not returned, and the add_folder and add_task write path in shipped version 1.1.7 does not permit an escape. This issue is fixed in repository version 1.1.9.