Skip to content
Noroxi
NVD / CVE Program· CNA jenkins

CVE-2022-25184: Jenkins Pipeline: Build Step Plugin 2.15 and earlier reveals password parameter default values when generating a pipeline script using the…

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.87% (FIRST EPSS); higher than 59.2% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: org.jenkins-ci.plugins:pipeline-build-step (Maven) 2.15.1; jenkins (Red Hat:openshift:3.11::el7) 0:2.319.3.1650348949-1.el7; jenkins-2-plugins (Red Hat:openshift:3.11::el7) 0:3.11.1650371376-1.el7.

Low priority for now. Upgrade to org.jenkins-ci.plugins:pipeline-build-step (Maven) 2.15.1; jenkins (Red Hat:openshift:3.11::el7) 0:2.319.3.1650348949-1.el7; jenkins-2-plugins (Red Hat:openshift:3.11::el7) 0:3.11.1650371376-1.el7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
Feb 15, 2022
Updated
Jun 17, 2026
EPSS
0.8% · 59th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-25184

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
jenkinspipeline\

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • jenkins pipeline: build stepup to 2.15 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (jenkins). Independent of NVD's CPE analysis and usually ahead of it.

  • Jenkins project Jenkins Pipeline: Build Step Plugin

    • 2.13.1not affected
    • unspecified and later · up to and including 2.15affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.jenkins-ci.plugins:pipeline-build-stepbefore 2.15.12.15.1
Red Hat:openshift:3.11::el7jenkinsbefore 0:2.319.3.1650348949-1.el70:2.319.3.1650348949-1.el7
Red Hat:openshift:3.11::el7jenkins-2-pluginsbefore 0:3.11.1650371376-1.el70:3.11.1650371376-1.el7
Red Hat:openshift:4.10::el8jenkins-2-pluginsbefore 0:4.10.1647505461-1.el80:4.10.1647505461-1.el8
Red Hat:openshift:4.6::el7haproxybefore 0:2.0.16-3.el70:2.0.16-3.el7
Red Hat:openshift:4.6::el7haproxy-debuginfobefore 0:2.0.16-3.el70:2.0.16-3.el7
Red Hat:openshift:4.6::el7haproxy20before 0:2.0.16-3.el70:2.0.16-3.el7
Red Hat:openshift:4.6::el8haproxybefore 0:2.0.16-5.el80:2.0.16-5.el8
Red Hat:openshift:4.6::el8haproxy-debugsourcebefore 0:2.0.16-5.el80:2.0.16-5.el8
Red Hat:openshift:4.6::el8haproxy20before 0:2.0.16-5.el80:2.0.16-5.el8
Red Hat:openshift:4.6::el8haproxy20-debuginfobefore 0:2.0.16-5.el80:2.0.16-5.el8
Red Hat:openshift:4.6::el8jenkins-2-pluginsbefore 0:4.6.1650364520-1.el80:4.6.1650364520-1.el8
Red Hat:openshift:4.7::el8jenkins-2-pluginsbefore 0:4.7.1648800585-1.el80:4.7.1648800585-1.el8
Red Hat:openshift:4.8::el7cri-obefore 0:1.21.5-3.rhaos4.8.gitaf64931.el70:1.21.5-3.rhaos4.8.gitaf64931.el7
Red Hat:openshift:4.8::el7cri-o-debuginfobefore 0:1.21.5-3.rhaos4.8.gitaf64931.el70:1.21.5-3.rhaos4.8.gitaf64931.el7
Red Hat:openshift:4.8::el8cri-obefore 0:1.21.5-3.rhaos4.8.gitaf64931.el80:1.21.5-3.rhaos4.8.gitaf64931.el8
Red Hat:openshift:4.8::el8cri-o-debuginfobefore 0:1.21.5-3.rhaos4.8.gitaf64931.el80:1.21.5-3.rhaos4.8.gitaf64931.el8
Red Hat:openshift:4.8::el8cri-o-debugsourcebefore 0:1.21.5-3.rhaos4.8.gitaf64931.el80:1.21.5-3.rhaos4.8.gitaf64931.el8
Red Hat:openshift:4.8::el8jenkins-2-pluginsbefore 0:4.8.1646993358-1.el80:4.8.1646993358-1.el8
Red Hat:openshift:4.9::el8haproxybefore 0:2.2.15-4.el80:2.2.15-4.el8
Red Hat:openshift:4.9::el8haproxy-debugsourcebefore 0:2.2.15-4.el80:2.2.15-4.el8
Red Hat:openshift:4.9::el8haproxy22before 0:2.2.15-4.el80:2.2.15-4.el8
Red Hat:openshift:4.9::el8haproxy22-debuginfobefore 0:2.2.15-4.el80:2.2.15-4.el8
Red Hat:openshift:4.9::el8jenkins-2-pluginsbefore 0:4.9.1647580879-1.el80:4.9.1647580879-1.el8

Other highest-scoring records for the same primary product.

  • CVE-2019-1003030A sandbox bypass vulnerability exists in Jenkins Pipeline: Groovy Plugin 2.63 and earlier in pom.xml…KEV
    98Now
  • CVE-2019-1003001A sandbox bypass vulnerability exists in Pipeline: Groovy Plugin 2.61 and earlier in…
    61This week
  • CVE-2019-1003002A sandbox bypass vulnerability exists in Pipeline: Declarative Plugin 1.3.3 and earlier in…
    59Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-25182Feb 15, 2022 · A sandbox bypass vulnerability in Jenkins Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier allows attackers with…
    35Monitor
  • ← EarlierCVE-2022-25183Feb 15, 2022 · Jenkins Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier uses the names of Pipeline libraries to create cache…
    35Monitor
  • Later →CVE-2022-28155Mar 29, 2022 · Jenkins Pipeline: Phoenix AutoTest Plugin 1.3 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.jenkins-ci.plugins:pipeline-build-step2.15.1Package registry (OSV)
red hat:cri-o0:1.21.5-3.rhaos4.8.gitaf64931.el7 · Red Hat:openshift:4.8::el7Package registry (OSV)
red hat:cri-o-debuginfo0:1.21.5-3.rhaos4.8.gitaf64931.el7 · Red Hat:openshift:4.8::el7Package registry (OSV)
red hat:cri-o-debugsource0:1.21.5-3.rhaos4.8.gitaf64931.el8 · Red Hat:openshift:4.8::el8Package registry (OSV)
red hat:haproxy0:2.2.15-4.el8 · Red Hat:openshift:4.9::el8Package registry (OSV)
red hat:haproxy-debuginfo0:2.0.16-3.el7 · Red Hat:openshift:4.6::el7Package registry (OSV)
red hat:haproxy-debugsource0:2.2.15-4.el8 · Red Hat:openshift:4.9::el8Package registry (OSV)
red hat:haproxy200:2.0.16-3.el7 · Red Hat:openshift:4.6::el7Package registry (OSV)
red hat:haproxy20-debuginfo0:2.0.16-5.el8 · Red Hat:openshift:4.6::el8Package registry (OSV)
red hat:haproxy220:2.2.15-4.el8 · Red Hat:openshift:4.9::el8Package registry (OSV)
red hat:haproxy22-debuginfo0:2.2.15-4.el8 · Red Hat:openshift:4.9::el8Package registry (OSV)
red hat:jenkins0:2.319.3.1650348949-1.el7 · Red Hat:openshift:3.11::el7Package registry (OSV)
red hat:jenkins-2-plugins0:4.8.1646993358-1.el8 · Red Hat:openshift:4.8::el8Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

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

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records