Authorization deception via unchecked OAuth scope names
Published Oct 5, 2021 · Updated Aug 4, 2024
OAuth scope spoofing in affected GitLab releases allows remote authenticated users to trick users into authorizing malicious clients. Application creation and update accept scope values without checking that they are a subset of predefined scopes, then display attacker-supplied scope text on the OAuth consent screen. A GitLab account is required to register the application, and a victim must open its authorization request and approve access, yielding an OAuth token to the attacker-controlled client.
Summary
What happened
OAuth scope spoofing in affected GitLab releases allows remote authenticated users to trick users into authorizing malicious clients. Application creation and update accept scope values without checking that they are a subset of predefined scopes, then display attacker-supplied scope text on the OAuth consent screen. A GitLab account is required to register the application, and a victim must open its authorization request and approve access, yielding an OAuth token to the attacker-controlled client.
The record
- CVE
- CVE-2021-39881
- Published
- Oct 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 5, 2021CVE 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=>=14.2, <14.2.5
- Affected versionversion=>=14.3, <14.3.1
- Affected versionversion=>=7.7, <14.1.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- OAuth scope-name spoofing proof of conceptproof of concept · demonstrated
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