GHSA-52hf-63q4-r926

## Summary The file `git.json.php` at the web root executes `git log -1` and returns the full output as JSON to any unauthenticated user. This exposes the exact deployed commit hash (enabling version fingerprinting against known CVEs), developer names and email addresses (PII), and commit messages which may contain references to internal systems or security fixes. ## Details `git.json.php` is a standalone PHP script with no authentication, no session validation, and no framework bootstrap. It directly executes a shell command and returns the result: ```php // git.json.php — complete file <?php header('Content-Type: application/json'); $cmd = "git log -1"; exec($cmd . " 2>&1", $output, $return_val); $obj = new stdClass(); $obj->output = $output; foreach ($output as $value) { preg_match("/Date:(.*)/i", $value, $match); if (!empty($match[1])) { $obj->date = strtotime($match[1]); $obj->dateString = trim($match[1]); $obj->dateMySQL = date("Y-m-d H:i:s", $obj->date); } } echo json_encode($obj); ``` The file does not `require` any configuration or authentication module. It is not protected by `.htaccess` rules. The endpoint is directly accessible to any network client. The exposed data enables: 1. **Version fingerprinting**: The commit hash identifies the exact deployed version, allowing attackers to cross-reference the project's public git history against known CVEs (AVideo has 22 published GHSAs) to determine which vulnerabilities remain unpatched on a given instance. 2. **Developer PII leakage**: Author name and email from the git commit are exposed. On self-hosted instances, this may reveal internal/corporate email addresses not otherwise publicly available. 3. **Commit message intelligence**: Commit messages may reference internal bug trackers, security fixes in progress, or infrastructure details. ## PoC ```bash # Single unauthenticated request — no cookies, no headers needed curl -s https://target.example/git.json.php