Device OAuth bypass via focusable user-code input
Published May 9, 2025 · Updated May 9, 2025
Authentication bypass in GitLab CE/EE allows remote attackers to submit Device OAuth authorization forms through minimal user interaction. The Device OAuth confirmation form retains an id on its user_code input, so a crafted URL fragment focuses that field and Enter submits the form. The victim must be signed in and press Enter; full bypass additionally requires Tab and Enter, granting the requesting OAuth client the approved scope.
Summary
What happened
Authentication bypass in GitLab CE/EE allows remote attackers to submit Device OAuth authorization forms through minimal user interaction. The Device OAuth confirmation form retains an id on its user_code input, so a crafted URL fragment focuses that field and Enter submits the form. The victim must be signed in and press Enter; full bypass additionally requires Tab and Enter, granting the requesting OAuth client the approved scope.
The record
- CVE
- CVE-2025-0549
- Published
- May 9, 2025
- Updated
- May 9, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-288, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2025CVE publishedPublication date reported by the CVE source.
- May 9, 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=17.10 <17.10.6
- Affected versionversion=17.11 <17.11.2
- Affected versionversion=17.3 <17.9.8
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
- Device OAuth cross-window forgery 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