CVE-2022-25184 is a medium-severity (CVSS 6.5) CWE-522 vulnerability in org.jenkins-ci.plugins:pipeline-build-step. A fix is available for org.jenkins-ci.plugins:pipeline-build-step — see the affected versions and patch details below.
Password parameter default values exposed by Jenkins Pipeline: Build Step Plugin
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-25184 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.jenkins-ci.plugins:pipeline-build-stepReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins Pipeline: Build Step Plugin 2.15 and earlier reveals password parameter default values when generating a pipeline script using the Pipeline Snippet Generator, allowing attackers with Item/Read permission to retrieve the default password parameter value from jobs.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:pipeline-build-step | all versions | 2.15.1org.jenkins-ci.plugins:pipeline-build-step:2.15.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:pipeline-build-step, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:pipeline-build-step to 2.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25184 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-25184 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-25184. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | jenkins-2-plugins-0:3.11.1650371376-1.el7 | RHSA-2022:1420 |
| Red Hat OpenShift Container Platform 4.10 | jenkins-2-plugins-0:4.10.1647505461-1.el8 | RHSA-2022:1025 |
| Red Hat OpenShift Container Platform 4.6 | jenkins-2-plugins-0:4.6.1650364520-1.el8 | RHSA-2022:1620 |
| Red Hat OpenShift Container Platform 4.7 | jenkins-2-plugins-0:4.7.1648800585-1.el8 | RHSA-2022:1248 |
| Red Hat OpenShift Container Platform 4.8 | jenkins-2-plugins-0:4.8.1646993358-1.el8 | RHSA-2022:0871 |
| Red Hat OpenShift Container Platform 4.9 | jenkins-2-plugins-0:4.9.1647580879-1.el8 | RHSA-2022:1021 |
Frequently Asked Questions
Is CVE-2022-25184 in your dependencies?
O3 Security finds CVE-2022-25184 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.