CVE-2022-43407

HIGH
8.8
CVSS Score
Published: October 19, 2022 at 12:00 AM UTC
Updated: June 17, 2026 at 05:06 AM UTC
2 products affected across 1 vendorPipeline: Input StepPipeline

Using Jenkins Pipeline: Input Step Plugin by Jenkins project?

Get instant alerts when new vulnerabilities affect Jenkins Pipeline: Input Step Plugin - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

Jenkins Pipeline: Input Step Plugin 451.vf1a_a_4f405289 and earlier does not restrict or sanitize the optionally specified ID of the 'input' step, which is used for the URLs that process user interactions for the given 'input' step (proceed or abort) and is not correctly encoded, allowing attackers able to configure Pipelines to have Jenkins build URLs from 'input' step IDs that would bypass the CSRF protection of any target URL in Jenkins when the 'input' step is interacted with.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≤ 451.vf1a_a_4f405289
Pipeline· Jenkinsjenkins-plugin
60%
v ≤ 451.vf1a_a_4f405289
Vendor states this is fixed in 449.451.v9c3d42f23975 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHCISA-ADP
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-352

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card