GitHub Enterprise Server up to 3.14.16/3.15.11/3.16.7/3.17.4 Compare/Diff authorization

Summaryinfo

A vulnerability was found in GitHub Enterprise Server up to 3.14.16/3.15.11/3.16.7/3.17.4 and classified as problematic. Affected by this issue is some unknown functionality of the component Compare/Diff. Executing a manipulation can lead to authorization. This vulnerability appears as CVE-2025-8447. The attack may be performed from remote. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in GitHub Enterprise Server up to 3.14.16/3.15.11/3.16.7/3.17.4. It has been declared as problematic. This vulnerability affects an unknown code of the component Compare/Diff. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect confidentiality. CVE summarizes:

An improper access control vulnerability was identified in GitHub Enterprise Server that allowed users with access to any repository to retrieve limited code content from another repository by creating a diff between the repositories. To exploit this vulnerability, an attacker needed to know the name of a private repository along with its branches, tags, or commit SHAs that they could use to trigger compare/diff functionality and retrieve limited code without proper authorization. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.18, and was fixed in versions 3.14.17, 3.15.12, 3.16.8 and 3.17.5. This vulnerability was reported via the GitHub Bug Bounty program.

The weakness was presented by furbreeze. The advisory is shared for download at docs.github.com. This vulnerability was named CVE-2025-8447 since 07/31/2025. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available.

Upgrading eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-1903). Once again VulDB remains the best source for vulnerability data.

Affected

• Microsoft GitHub Enterprise

Productinfo

Type

• Bug Tracking Software

Vendor

• GitHub

Name

• Enterprise Server

Version

• 3.14.0
• 3.14.1
• 3.14.2
• 3.14.3
• 3.14.4
• 3.14.5
• 3.14.6
• 3.14.7
• 3.14.8
• 3.14.9
• 3.14.10
• 3.14.11
• 3.14.12
• 3.14.13
• 3.14.14
• 3.14.15
• 3.14.16
• 3.15.0
• 3.15.1
• 3.15.2
• 3.15.3
• 3.15.4
• 3.15.5
• 3.15.6
• 3.15.7
• 3.15.8
• 3.15.9
• 3.15.10
• 3.15.11
• 3.16.0
• 3.16.1
• 3.16.2
• 3.16.3
• 3.16.4
• 3.16.5
• 3.16.6
• 3.16.7
• 3.17.0
• 3.17.1
• 3.17.2
• 3.17.3
• 3.17.4

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion