Authenticated code execution through Pages builds
Published Feb 17, 2022 · Updated Aug 4, 2024
Command injection in GitHub Enterprise Server before 3.3 allows remote authenticated users to execute code through GitHub Pages site builds. GitHub classifies the flaw as command injection but has not published the affected build component or how untrusted site content reaches a command invocation. Exploitation requires permission to create and build a Pages site, and successful exploitation executes code on the server.
Summary
What happened
Command injection in GitHub Enterprise Server before 3.3 allows remote authenticated users to execute code through GitHub Pages site builds. GitHub classifies the flaw as command injection but has not published the affected build component or how untrusted site content reaches a command invocation. Exploitation requires permission to create and build a Pages site, and successful exploitation executes code on the server.
The record
- CVE
- CVE-2021-41599
- Published
- Feb 17, 2022
- Updated
- Aug 4, 2024
- Vendor
- Product
- GitHub Enterprise Server
- Classifications
- CWE-77, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 17, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.0 <3.0.21
- Affected versionversion=3.1 <3.1.13
- Affected versionversion=3.2 <3.2.5
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