Pipeline\Application · Jenkins
CVE-2022-43408
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 · uneditedJenkins Pipeline: Stage View Plugin 2.26 and earlier does not correctly encode the ID of 'input' steps when using it to generate URLs to proceed or abort Pipeline builds, allowing attackers able to configure Pipelines to specify 'input' step IDs resulting in URLs that would bypass the CSRF protection of any target URL in Jenkins.
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 confidenceThe Pipeline: Stage View Plugin versions 2.26 and earlier fails to properly encode the ID parameter of 'input' steps when constructing URLs for proceeding or aborting Pipeline builds. Attackers with Pipeline configuration permissions can inject malicious input step IDs that allow crafted URLs to bypass Jenkins' CSRF protection mechanisms for any target URL.
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
< 2.27CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Pipeline: Stage View Plugin installationNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Pipeline: Stage View' in the list of installed pluginsAffected if The plugin is not installed or not found in the plugin list, the system is not affected by this specific vulnerability
-
Determine the installed version of Pipeline: Stage View PluginIn the plugin manager, locate Pipeline: Stage View and note the version number displayed in the 'Version' columnAffected if The installed version is 2.26 or earlier, indicating the vulnerable version is present
-
Verify if Pipeline input steps are used in job configurationsReview Pipeline job configurations (in Jenkinsfile or job settings) and look for 'input' step definitions, which are required for the vulnerability to be exploitableAffected if Pipeline jobs contain 'input' steps and the plugin version is 2.26 or earlier, the environment is affected by this vulnerability
-
Review Pipeline configuration permission assignmentsNavigate to Manage Jenkins > Manage and Assign Roles > Manage Roles and examine which users or groups have Pipeline configuration permissions (the ability to configure Pipeline builds)Affected if Users with untrusted or broad Pipeline configuration permissions exist and the plugin version is 2.26 or earlier, exploitation is possible
The environment is affected if Pipeline: Stage View Plugin version 2.26 or earlier is installed AND Pipeline jobs containing 'input' steps exist AND untrusted users have Pipeline configuration permissions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.27
Update Pipeline: Stage View Plugin to version 2.27 or later. Until the update is applied, restrict Pipeline configuration permissions to trusted users only.
Pipeline: Stage View Plugin version 2.27 or later
- Log in to Jenkins as an administrator
- Navigate to 'Manage Jenkins' > 'Manage Plugins'
- Click on the 'Installed' tab
- Locate the 'Pipeline: Stage View' plugin in the list
- Check the version number; if it is 2.26 or earlier, an update is available
- Select the plugin and click 'Update' to upgrade to version 2.27 or later
- After the update completes, restart Jenkins if required to apply the changes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pipeline\
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43408 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-43408 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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