Forced account login via missing OAuth state
Published Jan 24, 2023 · Updated Apr 2, 2025
Cross-site request forgery in Jenkins OpenID Plugin 2.4 and earlier allows remote attackers to force users into attacker accounts. The plugin starts its OAuth flow without a unique, non-guessable state parameter bound to the initiating authentication request. Exploitation requires user interaction with an attacker-controlled login flow and binds the victim's Jenkins activity to an account controlled by the attacker.
Summary
What happened
Cross-site request forgery in Jenkins OpenID Plugin 2.4 and earlier allows remote attackers to force users into attacker accounts. The plugin starts its OAuth flow without a unique, non-guessable state parameter bound to the initiating authentication request. Exploitation requires user interaction with an attacker-controlled login flow and binds the victim's Jenkins activity to an account controlled by the attacker.
The record
- CVE
- CVE-2023-24446
- Published
- Jan 24, 2023
- Updated
- Apr 2, 2025
- Vendor
- Jenkins Project
- Product
- Jenkins OpenID Plugin
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
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 <=2.4
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