Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2022-20621 — metrics

MEDIUMFix: jenkinsci/metrics-plugin@9810480

CVE-2022-20621 is a medium-severity (CVSS 5.5) CWE-522 vulnerability in org.jenkins-ci.plugins:metrics. A fix is available for org.jenkins-ci.plugins:metrics — see the affected versions and patch details below.

Access key stored in plain text by Jenkins Metrics Plugin

Also known asGHSA-gg9m-x3cg-69vh
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk
0.00%0.27%0.55%0.82%0.0%0.3%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2022-20621 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
☕org.jenkins-ci.plugins:metrics☕org.jenkins-ci.plugins:metrics

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Jenkins Metrics Plugin 4.0.2.8 and earlier stores an access key unencrypted in its global configuration file jenkins.metrics.api.MetricsAccessKey.xml on the Jenkins controller as part of its configuration.

This access key can be viewed by users with access to the Jenkins controller file system.

Jenkins Metrics Plugin 4.0.2.8.1 stores access key encrypted once its configuration is saved again.

Additionally, the token value is only displayed once when it is generated.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jenkins-ci.plugins:metrics≥ 4.0.2.8&&< 4.0.2.8.14.0.2.8.1org.jenkins-ci.plugins:metrics:4.0.2.8.1
☕Mavenorg.jenkins-ci.plugins:metricsall versions4.0.2.7.1org.jenkins-ci.plugins:metrics:4.0.2.7.1

Affected Products

1 product · 1 configurations
Application
metricsjenkins
≤ 4.0.2.8
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:metrics, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.jenkins-ci.plugins:metrics to 4.0.2.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-20621 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Jenkins Metrics Plugin 4.0.2.8 and earlier stores an access key unencrypted in its global configuration file `jenkins.metrics.api.MetricsAccessKey.xml` on the Jenkins controller as part of its configuration. This access key can be viewed by users with access to the Jenkins controller file system. Jenkins Metrics Plugin 4.0.2.8.1 stores access key encrypted once its configuration is saved again. Additionally, the token value is only displayed once when it is generated.
O3 Security · Impact-Aware SCA

Is CVE-2022-20621 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-20621: metrics — Fixed in 4.0.2.8.1