Cross-group workflow execution via improper authentication
Published Sep 24, 2021 · Updated Aug 3, 2024
GitHub Enterprise Server 3.0.0 through 3.0.15 and 3.1.0 through 3.1.7 allows attackers to run jobs in unauthorized runner groups. The workflow-job request path failed to verify that the requesting repository could access the selected enterprise runner group. Exploitation requires repository access and configured self-hosted runner groups, and it executes workflow code on an unintended runner group.
Summary
What happened
GitHub Enterprise Server 3.0.0 through 3.0.15 and 3.1.0 through 3.1.7 allows attackers to run jobs in unauthorized runner groups. The workflow-job request path failed to verify that the requesting repository could access the selected enterprise runner group. Exploitation requires repository access and configured self-hosted runner groups, and it executes workflow code on an unintended runner group.
The record
- CVE
- CVE-2021-22869
- Published
- Sep 24, 2021
- Updated
- Aug 3, 2024
- Vendor
- Product
- GitHub Enterprise Server
- Classifications
- CWE-668, CWE-287
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 24, 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=3.0 <3.0.16
- Affected versionversion=3.1 <3.1.8
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