Skip to content
Fencer Intel
high 8.8

CVE-2022-36889 json

Jenkins Deployer Framework Plugin does not restrict application path of applications when configuring a deployment

published 4y ago modified 4mo ago also GHSA-j5qq-6rpm-qjgh , EUVD-2022-6360

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.jenkins-ci.plugins:deployer-framework 86.v7b_a_4a_55b_f3ec
  • Jenkins project Jenkins Deployer Framework Plugin 1.3.1

Is CVE-2022-36889 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

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins:deployer-framework
<86.v7b_a_4a_55b_f3ec
86.v7b_a_4a_55b_f3ec

Affected products

  • Jenkins project Jenkins Deployer Framework Plugin

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

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.