Authenticated file read via Pages path traversal
Published Jul 14, 2021 · Updated Aug 3, 2024
Path traversal in GitHub Pages builds on GitHub Enterprise Server before 3.1.3 allows remote authenticated users to read instance files. The Pages build pipeline accepts user-controlled configuration options without sufficient path restrictions, allowing configured paths to escape the intended build area. Exploitation requires permission to create and build a GitHub Pages site, and the demonstrated consequence is reading files from the server instance.
Summary
What happened
Path traversal in GitHub Pages builds on GitHub Enterprise Server before 3.1.3 allows remote authenticated users to read instance files. The Pages build pipeline accepts user-controlled configuration options without sufficient path restrictions, allowing configured paths to escape the intended build area. Exploitation requires permission to create and build a GitHub Pages site, and the demonstrated consequence is reading files from the server instance.
The record
- CVE
- CVE-2021-22867
- Published
- Jul 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Product
- GitHub Enterprise Server
- Classifications
- CWE-22, CWE-77, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=2.22 <2.22.17
- Affected versionversion=3.0 <3.0.11
- Affected versionversion=3.1 <3.1.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.
Weakness, pattern, technique
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