Account takeover via unconfirmed JWT identity linking
Published Jan 30, 2025 · Updated Jan 31, 2025
CSRF in affected GitLab CE/EE releases allows remote authenticated users to take over accounts through JWT OmniAuth identity linking. The OmniAuth callback flow linked a JWT-provided identity to an existing account without requiring the account owner to confirm the link. Exploitation requires JWT OmniAuth, an authenticated attacker, and victim interaction; a successful link grants access to the victim's account.
Summary
What happened
CSRF in affected GitLab CE/EE releases allows remote authenticated users to take over accounts through JWT OmniAuth identity linking. The OmniAuth callback flow linked a JWT-provided identity to an existing account without requiring the account owner to confirm the link. Exploitation requires JWT OmniAuth, an authenticated attacker, and victim interaction; a successful link grants access to the victim's account.
The record
- CVE
- CVE-2024-1211
- Published
- Jan 30, 2025
- Updated
- Jan 31, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-352, T1098.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 30, 2025CVE publishedPublication date reported by the CVE source.
- Jan 31, 2025Record 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=10.6 <16.9.7
- Affected versionversion=16.10 <16.10.5
- Affected versionversion=16.11 <16.11.2
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