Skip to content
Fencer Vulns
medium 5.5

CVE-2022-20621 json

Access key stored in plain text by Jenkins Metrics Plugin

published 2022-01-12 4 y ago modified 2026-06-17 4 mo ago also GHSA-gg9m-x3cg-69vh , EUVD-2022-0602

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

Summary

Jenkins Metrics Plugin 4.0.2.8 and earlier stores an access key unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.

Patch / fix

  • maven org.jenkins-ci.plugins:metrics 4.0.2.7.1, 4.0.2.8.1
  • Jenkins project Jenkins Metrics Plugin 4.0.2.7.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-20621 updated cvss 5.5

jenkins-2-plugins/metrics: stores access keys unencrypted in its global configuration file

  • Red Hat OpenShift Container Platform 3.11 jenkins-2-plugins
    affected: no fix available “Fix deferred”
  • Red Hat OpenShift Container Platform 4 jenkins-2-plugins
    affected: no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 5.5 CVSS:3.1/AV:L/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:metrics
>=4.0.2.8, <4.0.2.8.1
<4.0.2.7.1
4.0.2.8.1
4.0.2.7.1

Affected products

  • Jenkins project Jenkins Metrics Plugin

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials

References

Sources

Fencer Vulns 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.