How severe is CVE-2022-25184?

CVE-2022-25184 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-25184?

CVE-2022-25184 affects the following packages: org.jenkins-ci.plugins:pipeline-build-step (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-25184?

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.

How do I detect CVE-2022-25184 in my Maven dependencies?

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.

How do I mitigate CVE-2022-25184 if there is no patch (or I can't update yet)?

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.

Is CVE-2022-25184 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-25184 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-25184?

CVE-2022-25184 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-25184?

CVE-2022-25184 is classified as CWE-522 (CWE-522). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-25184 published, and has it been updated?

CVE-2022-25184 was published on February 15, 2022 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2022-25184 — pipeline-build-step

MEDIUMFix: jenkinsci/pipeline-build-step-plugin@c06f654

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

Also known asGHSA-g84f-cmc8-682c

Published

Feb 15, 2022

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:pipeline-build-step

Real-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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:pipeline-build-step`	all versions	2.15.1`org.jenkins-ci.plugins:pipeline-build-step:2.15.1`

Affected Products

1 product · 1 configurations

Application

pipeline\jenkins

≤ 2.15

1 version

_build_step

Detection & mitigation playbook

Open-source dependency

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

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.

Red HatModerate

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

O3 Security · Impact-Aware SCA

Is CVE-2022-25184 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-522CWE-522

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Feb 15, 2022

Last updated

Oct 24, 2026

Identifiers

CVE-2022-25184

GHSA-g84f-cmc8-682c

References

Advisorynvd.nist.gov · CVE 2022 25184 Fixjenkins.io · 2022 02 15 Webgithub.com · c06f65425fe9696d2237f591959dd4b5c6083fd9 Packagegithub.com · pipeline build step plugin

Related vulnerabilities

Also affects pipeline-build-step

This CVE is medium severity, in line with the other 3 CVEs affecting pipeline-build-step.

CVE-2023-25762CVE-2020-2118CVE-2017-1000089

Same weakness: CWE-522

This CVE is medium severity; 5 of 5 other CVEs with CWE-522 are rated as high or higher (top: critical).

CVE-2026-105769CVE-2026-118763CVE-2026-116683GHSA-vqqp-x5qm-5qp4CVE-2026-111765Browse all CWE-522

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2022-25184 — pipeline-build-step

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-25184 in your dependencies?