Repository page modification via improper API authorization
Published Dec 1, 2022 · Updated Apr 24, 2025
Improper privilege management in affected GitHub Enterprise Server 3.2 through 3.6 releases allows remote authenticated users to modify pages. The repository pages API accepts create or delete operations from users whose repository write role is insufficient for those page-management actions. An attacker must first be added to an organization's repository with write permission; the documented consequence is unauthorized page creation or deletion.
Summary
What happened
Improper privilege management in affected GitHub Enterprise Server 3.2 through 3.6 releases allows remote authenticated users to modify pages. The repository pages API accepts create or delete operations from users whose repository write role is insufficient for those page-management actions. An attacker must first be added to an organization's repository with write permission; the documented consequence is unauthorized page creation or deletion.
The record
- CVE
- CVE-2022-23737
- Published
- Dec 1, 2022
- Updated
- Apr 24, 2025
- Vendor
- Product
- GitHub Enterprise Server
- Classifications
- CWE-269, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 1, 2022CVE publishedPublication date reported by the CVE source.
- Apr 24, 2025Record 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.2 <3.2.20
- Affected versionversion=3.3 <3.3.15
- Affected versionversion=3.4 <3.4.10
- Affected versionversion=3.5 <3.5.7
- Affected versionversion=3.6 <3.6.3
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