Forced account-bound login via missing OAuth state
Published Jan 24, 2023 · Updated Apr 2, 2025
Cross-site request forgery in Jenkins Bitbucket OAuth Plugin 0.12 and earlier allows attackers to force account-bound logins. The OAuth commence-login and finish-login handlers omit generation, transport, and validation of a session-bound state value. Exploitation requires user interaction with an attacker-initiated OAuth authorization flow and binds the resulting Jenkins session to the attacker's Bitbucket account.
Summary
What happened
Cross-site request forgery in Jenkins Bitbucket OAuth Plugin 0.12 and earlier allows attackers to force account-bound logins. The OAuth commence-login and finish-login handlers omit generation, transport, and validation of a session-bound state value. Exploitation requires user interaction with an attacker-initiated OAuth authorization flow and binds the resulting Jenkins session to the attacker's Bitbucket account.
The record
- CVE
- CVE-2023-24428
- Published
- Jan 24, 2023
- Updated
- Apr 2, 2025
- Vendor
- Jenkins Project
- Product
- Bitbucket OAuth
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2023CVE publishedPublication date reported by the CVE source.
- Apr 2, 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=unspecified <=0.12
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.
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