Approved changes feed: RSS · Atom

cpe:2.3:a:jenkins:pipeline\:_input_step:*:*:*:*:*:jenkins:*:*

part: a version: * update: *

VendorJenkins (d708d718-2e77-5ca3-ae9c-38ee4d256744)
ProductPipeline: Input Step (fd9a6b79-ffa9-5d9d-9dc0-f45b8af8d364)
Edition*
Language*
Software edition*
Target softwarejenkins
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2022-43407 vulnerable 2026-06-08 05:49:31.787703 Details available
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.
Published: 2022-10-19T00:00:00.000Z
Updated: 2025-05-08T19:25:25.222Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-34177 vulnerable 2026-06-08 05:44:52.369996 Details available
Jenkins Pipeline: Input Step Plugin 448.v37cea_9a_10a_70 and earlier archives files uploaded for `file` parameters for Pipeline `input` steps on the controller as part of build metadata, using the parameter name without sanitization as a relative path inside a build-related directory, allowing attackers able to configure Pipelines to create or replace arbitrary files on the Jenkins controller file system with attacker-specified content.
Published: 2022-06-22T00:00:00.000Z
Updated: 2024-08-03T08:16:17.208Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.