OAuth token misissuance via incorrect client selection
Published Aug 25, 2021 · Updated Aug 3, 2024
Incorrect authorization in GitLab CE/EE 14.1.0 through 14.1.1 allows remote authenticated users to receive misissued OAuth tokens. The subscription-creation path mishandles OAuth client identifiers and generates each new subscription token for the wrong OAuth client application. Exploitation requires low-privileged network access and user interaction; the public vendor record does not identify the affected endpoint or further bound token capabilities.
Summary
What happened
Incorrect authorization in GitLab CE/EE 14.1.0 through 14.1.1 allows remote authenticated users to receive misissued OAuth tokens. The subscription-creation path mishandles OAuth client identifiers and generates each new subscription token for the wrong OAuth client application. Exploitation requires low-privileged network access and user interaction; the public vendor record does not identify the affected endpoint or further bound token capabilities.
The record
- CVE
- CVE-2021-22236
- Published
- Aug 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 25, 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=>=14.1, <14.1.2
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
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