Relying-party account takeover via unverified OAuth email
Published Jun 19, 2020 · Updated Aug 4, 2024
Improper OAuth authorization in GitLab allows remote authenticated users to obtain authorization codes for accounts with unverified email addresses. The OAuth authorization endpoint issues a code after login without checking whether the account's primary email address has been verified. An attacker must register and authenticate an account with an unverified address; relying applications that trust GitLab email claims can then bind access to an address the attacker does not own.
Summary
What happened
Improper OAuth authorization in GitLab allows remote authenticated users to obtain authorization codes for accounts with unverified email addresses. The OAuth authorization endpoint issues a code after login without checking whether the account's primary email address has been verified. An attacker must register and authenticate an account with an unverified address; relying applications that trust GitLab email claims can then bind access to an address the attacker does not own.
The record
- CVE
- CVE-2020-13272
- Published
- Jun 19, 2020
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-345, T1136
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 2020CVE 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=>=12.10, <12.10.7
- Affected versionversion=>=12.3, <12.9.8
- Affected versionversion=>=13.0, <13.0.1
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 Web Application Flow reproduction stepsproof 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