Skip to content
Fencer Intel
medium 4.3

CVE-2020-2239 json

Secret stored in plain text by Jenkins Parameterized Remote Trigger Plugin

published 6y ago modified 4mo ago also GHSA-wphq-j78p-fhgp , EUVD-2022-5614

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

Summary

Jenkins Parameterized Remote Trigger Plugin 3.1.3 and earlier stores a secret unencrypted in its global configuration file on the Jenkins controller where it can be viewed by attackers with access to the Jenkins controller file system.

Patch / fix

  • maven org.jenkins-ci.plugins:Parameterized-Remote-Trigger 3.1.4

Is CVE-2020-2239 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

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

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins:Parameterized-Remote-Trigger
<3.1.4
3.1.4

Affected products

  • Jenkins project Jenkins Parameterized Remote Trigger Plugin

Classification

Weakness
  • CWE-311 Missing Encryption of Sensitive Data
  • CWE-256 Plaintext Storage of a Password

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.