Commit smuggling via incorrect reopened pull-request diff
Published Aug 30, 2023 · Updated Sep 27, 2024
Incorrect comparison in GitHub Enterprise Server allows remote authenticated users to smuggle commits through reopened pull requests. The reopened-pull-request diff performs an incorrect comparison, but GitHub has not disclosed the compared values or implementation locus. Repository write access and a reviewer viewing the reopened pull request are required; the misleading diff can conceal source-branch commits during review.
Summary
What happened
Incorrect comparison in GitHub Enterprise Server allows remote authenticated users to smuggle commits through reopened pull requests. The reopened-pull-request diff performs an incorrect comparison, but GitHub has not disclosed the compared values or implementation locus. Repository write access and a reviewer viewing the reopened pull request are required; the misleading diff can conceal source-branch commits during review.
The record
- CVE
- CVE-2023-23765
- Published
- Aug 30, 2023
- Updated
- Sep 27, 2024
- Vendor
- Product
- GitHub Enterprise Server
- Classifications
- CWE-697, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 30, 2023CVE publishedPublication date reported by the CVE source.
- Sep 27, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.6.0 <3.6.16
- Affected versionversion=3.7.0 <3.7.13
- Affected versionversion=3.8.0 <3.8.6
- Affected versionversion=3.9.0 <3.9.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo