dbcve.org
Deployer FrameworkApplication · Jenkins

CVE-2022-36889

HIGH · 8.8 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to after 85.v1d1888e8c021 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Jenkins Deployer Framework Plugin 85.v1d1888e8c021 and earlier does not restrict the application path of the applications when configuring a deployment, allowing attackers with Item/Configure permission to upload arbitrary files from the Jenkins controller file system to the selected service.

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 confidence

The Jenkins Deployer Framework Plugin versions 85.v1d1888e8c021 and earlier lacks path validation when configuring deployment application paths, allowing authenticated users with Item/Configure permission to perform path traversal and upload arbitrary files from the Jenkins controller filesystem to configured deployment targets.

MitigationUpgrade to the patched version of the Deployer Framework Plugin and restrict Item/Configure permission to trusted users only, as the vulnerability requires Configure permission on items.

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
Deployer FrameworkApplication
Affected:<= 85.v1d1888e8c021

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Deployer Framework Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed and search for 'Deployer Framework' or list installed plugins via Jenkins CLI: jenkins-cli.jar or REST API /pluginManager/api/json?tree=plugins[shortName,version]
    Affected if The Deployer Framework plugin appears in the installed plugins list
  2. Verify the installed plugin version
    In the Installed Plugins tab, find the Deployer Framework plugin and note the version number displayed, or query the REST API endpoint /pluginManager/api/json?tree=plugins[shortName,version]{&where=shortName=='deployer-framework'}
    Affected if The version is 85.v1d1888e8c021 or earlier
  3. Check for configured deployment targets
    Navigate to the job or item configuration pages and look for Deployer Framework build steps or configuration sections that specify deployment application paths, or inspect job config.xml files for 'deployer' or 'Deployment' related elements
    Affected if A deployment configuration exists that uses the Deployer Framework plugin with configurable application paths
  4. Audit Item/Configure permission assignments
    Review Global Security settings and per-item permissions to identify which users or groups have Item/Configure permission, or query /api/json?tree=users[id,fullName] and check authorization matrix configurations
    Affected if Users or groups beyond trusted administrators have Item/Configure permission on items using Deployer Framework deployments

You are affected if the Deployer Framework plugin version 85.v1d1888e8c021 or earlier is installed AND deployment configurations exist AND untrusted users have Item/Configure permission on those items.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 85.v1d1888e8c021
Interim mitigation

Upgrade to the patched version of the Deployer Framework Plugin and restrict Item/Configure permission to trusted users only, as the vulnerability requires Configure permission on items.

Recommended fix Moderate confidence

Deployer Framework plugin version > 85.v1d1888e8c021 (check Jenkins Update Center for latest available version)

  1. Check the Jenkins Update Center for the latest version of the Deployer Framework plugin
  2. Navigate to Manage Jenkins > Manage Plugins > Available
  3. Locate the Deployer Framework plugin and update to the latest version
  4. Restart Jenkins if required for the update to take effect
  5. Verify the new version is installed under Manage Jenkins > Manage Plugins > Installed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Deployer Framework Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36889 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36889 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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