CSRF bypass via unencoded input step IDs
Published Oct 19, 2022 · Updated May 8, 2025
CSRF in Jenkins Pipeline: Stage View Plugin 2.26 and earlier allows remote authenticated users to invoke arbitrary Jenkins URLs. The plugin places an attacker-controlled input step ID into proceed or abort URLs without correct encoding, allowing the path to target another Jenkins endpoint. Exploitation requires Pipeline configuration access, victim interaction with the crafted input step, and Pipeline: Input Step Plugin 451.vf1a_a_4f405289 or earlier; the request carries the victim's authority.
Summary
What happened
CSRF in Jenkins Pipeline: Stage View Plugin 2.26 and earlier allows remote authenticated users to invoke arbitrary Jenkins URLs. The plugin places an attacker-controlled input step ID into proceed or abort URLs without correct encoding, allowing the path to target another Jenkins endpoint. Exploitation requires Pipeline configuration access, victim interaction with the crafted input step, and Pipeline: Input Step Plugin 451.vf1a_a_4f405289 or earlier; the request carries the victim's authority.
The record
- CVE
- CVE-2022-43408
- Published
- Oct 19, 2022
- Updated
- May 8, 2025
- Vendor
- Jenkins Project
- Product
- Pipeline: Stage View
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 19, 2022CVE publishedPublication date reported by the CVE source.
- May 8, 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.26
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