dbcve.org
Pipeline\Application · Jenkins

CVE-2022-43407

HIGH · 8.8 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to after 451.vf1a_a_4f405289 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Jenkins Pipeline: Input Step Plugin (versions 451.vf1a_a_4f405289 and earlier) fails to properly sanitize or restrict the optionally specified ID parameter of the 'input' step. This ID is used to construct URLs for user interactions (proceed/abort), and when not correctly encoded, allows attackers with pipeline configuration privileges to craft malicious IDs that bypass CSRF protection on any target URL in Jenkins.

MitigationUpgrade Jenkins Pipeline: Input Step Plugin to the latest version that properly encodes the input step ID and implements proper input validation to prevent CSRF bypass.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pipeline\Application
Affected:<= 451.vf1a_a_4f405289

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Pipeline: Input Step Plugin is installed
    Go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Pipeline: Input Step', or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | findstr 'pipeline-input-step'
    Affected if The plugin is not installed (not vulnerable) or is installed but version is unknown or higher than 451.vf1a_a_4f405289 (not vulnerable)
  2. Confirm installed version is within affected range
    In Manage Jenkins > Manage Plugins > Installed, check the version column for Pipeline: Input Step Plugin. Compare against 451.vf1a_a_4f405289 (any version equal to or lower is affected)
    Affected if Installed version is 451.vf1a_a_4f405289 or earlier
  3. Identify pipelines using the 'input' step
    Search job configurations for occurrences of the 'input' step in Jenkinsfiles or job configurations. Use Jenkins script console: Jenkins.instance.allItems.collect { it.class.name + ': ' + it.name }.findAll { it.contains('input') } or search SCM/repositories for 'input {' pattern
    Affected if Pipelines exist that use the 'input' step, making CSRF bypass possible if malicious ID is supplied

User is affected if Pipeline: Input Step Plugin version 451.vf1a_a_4f405289 or earlier is installed AND pipelines using the 'input' step exist in the environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 451.vf1a_a_4f405289
Interim mitigation

Upgrade Jenkins Pipeline: Input Step Plugin to the latest version that properly encodes the input step ID and implements proper input validation to prevent CSRF bypass.

Recommended fix High confidence

Pipeline: Input Step Plugin version 452.vf1a_a_4f4067c or later

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Select the 'Updates' tab and check for Pipeline: Input Step Plugin
  3. Update the plugin to the latest available version (452.vf1a_a_4f4067c or later)
  4. Restart Jenkins if required by the update process
  5. Verify the input step functions correctly in existing pipelines

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pipeline\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43407 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-43407 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data