Skip to content
Fencer Intel
medium 6.5

CVE-2022-43408 json

Jenkins Pipeline: Stage View Plugin allows CSRF protection bypass of any target URL in Jenkins

published 4y ago modified 4mo ago also GHSA-g975-f26h-93g8 , EUVD-2022-7096

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

Jenkins 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.

Patch / fix

  • maven org.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view 2.24.2, 2.27
  • Jenkins project Jenkins Pipeline: Stage View Plugin 2.24.2
  • jenkins openshift 4.9 2.361.1.1675668150-1.el8
  • jenkins-2-plugins openshift 4.9 4.9.1675668922-1.el8
  • jenkins ocp tools 4.11 2.387.1.1683009763-3.el8
  • jenkins-2-plugins ocp tools 4.11 4.11.1683009941-1.el8
  • jenkins-2-plugins openshift 4.10 4.10.1675144701-1.el8
  • jenkins-2-plugins ocp tools 4.12 4.12.1675702407-1.el8

red hat advisories RHSA-2023:0777RHSA-2023:3198RHSA-2023:0560RHSA-2023:1064

Is CVE-2022-43408 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-43408 updated cvss 5.7

jenkins-plugin/pipeline-stage-view: CSRF protection for any URL can be bypassed in Pipeline: Stage View Plugin

  • Red Hat OpenShift Enterprise 3 jenkins-2-plugins
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat OpenShift Developer Tools and Services for OCP 4.11 for RHEL 8 jenkins-2-plugins 4.11.1683009941-1.el8
    fixed: vendor fix RHSA-2023:3198
  • Red Hat OpenShift Developer Tools and Services for OCP 4.12 jenkins-2-plugins 4.12.1675702407-1.el8
    fixed: vendor fix RHSA-2023:1064
  • Red Hat OpenShift Container Platform 4.9 jenkins-2-plugins 4.9.1675668922-1.el8
    fixed: vendor fix RHSA-2023:0777
  • Red Hat OpenShift Container Platform 4.10 jenkins-2-plugins 4.10.1675144701-1.el8
    fixed: vendor fix RHSA-2023:0560
  • Red Hat OpenShift Developer Tools and Services for OCP 4.11 for RHEL 8 jenkins 2.387.1.1683009763-3.el8 Red Hat OpenShift Developer Tools and Services for OCP 4.12 jenkins 2.361.4.1675702346-3.el8 Red Hat OpenShift Container Platform 4.9 jenkins 2.361.1.1675668150-1.el8 Red Hat OpenShift Container Platform 4.10 cri-o 1.23.5-5.rhaos4.10.gitd9dec98.el7, cri-o 1.23.5-5.rhaos4.10.gitd9dec98.el8
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
GitHub 3.1 8.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view
>=2.25, <2.27
<2.24.2
2.27
2.24.2

Affected products

  • Jenkins project Jenkins Pipeline: Stage View Plugin

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery
  • CWE-838 Inappropriate Encoding for Output Context

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.