Unintended permission grants via incomplete reauthorization display
Published May 14, 2021 · Updated Aug 3, 2024
GitHub Enterprise Server 2.22.0 through 2.22.12 and 3.0.0 through 3.0.6 has UI misrepresentation allowing attackers unintended permissions. The GitHub App reauthorization screen omits newly requested user-level permissions in certain revisits while the authorization flow still grants them. Exploitation requires an attacker-created GitHub App and a user who authorized it once to revisit the flow after the app adds permissions, exposing resources covered by the undisclosed grants.
Summary
What happened
GitHub Enterprise Server 2.22.0 through 2.22.12 and 3.0.0 through 3.0.6 has UI misrepresentation allowing attackers unintended permissions. The GitHub App reauthorization screen omits newly requested user-level permissions in certain revisits while the authorization flow still grants them. Exploitation requires an attacker-created GitHub App and a user who authorized it once to revisit the flow after the app adds permissions, exposing resources covered by the undisclosed grants.
The record
- CVE
- CVE-2021-22866
- Published
- May 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Product
- GitHub Enterprise Server
- Classifications
- CWE-1021, CWE-451
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 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.13
- Affected versionversion=3.0 <3.0.7
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