CVE-2023-237626.5MediumCWE-697

CVE-2023-23762: Incorrect comparison vulnerability in GitHub Enterprise Server leading to commit smuggling

GitHub · Enterprise Server

Vendor fix available · Affected: GitHub Enterprise Server · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.6%probability of exploitation in the next 30 days

51st percentile

050100

Higher than 51% of scored CVEs

6.5MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

An incorrect comparison vulnerability was identified in GitHub Enterprise Server that allowed commit smuggling by displaying an incorrect diff. To do so, an attacker would need write access to the repository and be able to correctly guess the target branch before it’s created by the code maintainer. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.9 and was fixed in versions 3.4.18, 3.5.15, 3.6.11, 3.7.8, and 3.8.1. This vulnerability was reported via the GitHub Bug Bounty program.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

GitHub · Enterprise Serverfrom 3.4.0 up to and including 3.4.17; from 3.5.0 up to and including 3.5.14; from 3.6.0 up to and including 3.6.10; from 3.7.0 up to and including 3.7.7; from 3.8.0 before 3.8.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Incorrect Comparison · Input Validation and Logic
Vendor: GitHub
Published: April 2023
Band: Unlikely (under 1%), April 2023
Bounty reports: 1 disclosed on HackerOne

Disclosed bug bounty reports about CVE-2023-23762

The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.

Rogue collaborators and ambiguous branch names in GitHubGitHub · 2023Valid

CoverageNo articles yet

No CyberSIXT article names CVE-2023-23762 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.