For your digest
org.jenkins-ci.plugins:pipeline-input-step: CSRF protection for any URL can be bypassed in Jenkins Pipeline: Input Step Plugin
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
org.jenkins-ci.plugins:pipeline-input-step (Maven)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- org.jenkins-ci.plugins:pipeline-input-step (Maven): every version, before 456.vd8a_957db_5b_e9
The fix
org.jenkins-ci.plugins:pipeline-input-step (Maven) fixed in 456.vd8a_957db_5b_e9
mavenmvn versions:use-dep-version -Dincludes=org.jenkins-ci.plugins:pipeline-input-step -DdepVersion=456.vd8a_957db_5b_e9 -DforceVersion=trueCheck what is installedmvn dependency:tree -Dincludes=org.jenkins-ci.plugins:pipeline-input-stepPaste into Cursor, Lovable or Claude CodeUpgrade the Maven dependency org.jenkins-ci.plugins:pipeline-input-step to 456.vd8a_957db_5b_e9 or the nearest later release, to fix CVE-2022-43407. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".