CyberRota Analysis
AI-GeneratedAuthenticated users with write access on GitHub Enterprise Server can exploit a missing authorization vulnerability to access metadata from private repositories they do not have permission to view, potentially exposing sensitive information such as repository owners, branch names, and commit details. This issue affects all versions prior to 3.22 and should be prioritized by organizations using GitHub Enterprise Server to mitigate unauthorized data exposure risks. Immediate updates to the patched versions are recommended to secure affected instances.
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
A missing authorization vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user with write access to any repository to read metadata from private repositories they did not have access to, including private repository owners and names, branch names, commit SHAs, commit messages, and the pushing actor. The delegated bypass endpoint resolved a rule suite directly from an attacker-supplied, encoded identifier without verifying that the requesting user could read the rule suite's repository, and because these identifiers are sequential an attacker could enumerate them across the instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.18, 3.18.12, 3.19.9, 3.20.5, and 3.21.3. This vulnerability was reported via the GitHub Bug Bounty program.