Excess permissions via incomplete reauthorization display
Published Jan 25, 2022 · Updated Aug 4, 2024
UI misrepresentation in affected GitHub Enterprise Server 3.0, 3.1, and 3.2 releases allows attackers to obtain extra app permissions. During repository-scope updates, the user-authorization flow omits newly configured user-level permissions from the approval display while still granting them. Exploitation requires an attacker-created GitHub App, initial user authorization, and a later repository-set change, leaving the app with permissions beyond those displayed during reauthorization.
Summary
What happened
UI misrepresentation in affected GitHub Enterprise Server 3.0, 3.1, and 3.2 releases allows attackers to obtain extra app permissions. During repository-scope updates, the user-authorization flow omits newly configured user-level permissions from the approval display while still granting them. Exploitation requires an attacker-created GitHub App, initial user authorization, and a later repository-set change, leaving the app with permissions beyond those displayed during reauthorization.
The record
- CVE
- CVE-2021-41598
- Published
- Jan 25, 2022
- Updated
- Aug 4, 2024
- Vendor
- Product
- GitHub Enterprise Server
- Classifications
- CWE-451
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 25, 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