NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
LOW severity

Improper masking of some secrets in Jenkins Credentials Binding PluginGHSA-7ff8-qfwx-8gx5

LOWFix: jenkinsci/credentials-binding-plugin@77681e0

GHSA-7ff8-qfwx-8gx5 is a low-severity (CVSS 3.1) CWE-522 vulnerability in org.jenkins-ci.plugins:credentials-binding. A fix is available for org.jenkins-ci.plugins:credentials-binding — see the affected versions and patch details below.

Also known asCVE-2020-2182
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.00%0.47%0.93%1.40%0.0%0.9%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕org.jenkins-ci.plugins:credentials-binding

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

Credentials Binding Plugin allows specifying passwords and other secrets as environment variables, and will hide them from console output in builds. As a side effect of the fix for SECURITY-698, $ characters in secrets are escaped to $$. This will then be expanded to $ again once the secret is passed to (post) build steps.

Credentials Binding Plugin 1.22 and earlier does not mask the escaped form of the secret (containing $$). This occurs for example in the "Execute Maven top-level targets" build step included in Jenkins.\n\nCredentials Binding Plugin 1.23 now masks secrets both in their original form and with escaped $ characters, so they will be masked even if printed before value expansion.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jenkins-ci.plugins:credentials-bindingall versions1.23org.jenkins-ci.plugins:credentials-binding:1.23

Affected Products

1 product · 1 configurations
Application
credentials bindingjenkins
≤ 1.22
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:credentials-binding, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.jenkins-ci.plugins:credentials-binding to 1.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7ff8-qfwx-8gx5 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow
ProductFixed inAdvisory
Red Hat OpenShift Container Platform 3.11atomic-enterprise-service-catalog-1:3.11.248-1.git.1.9aad2ef.el7RHBA-2020:2990
Red Hat OpenShift Container Platform 4.3jenkins-2-plugins-0:4.3.1601981312-1.el7RHSA-2020:4265
Red Hat OpenShift Container Platform 4.4jenkins-2-plugins-0:4.4.1598545590-1.el7RHSA-2020:3625
Red Hat OpenShift Container Platform 4.5jenkins-2-plugins-0:4.5.1596698303-1.el7RHSA-2020:3453

Frequently Asked Questions

Credentials Binding Plugin allows specifying passwords and other secrets as environment variables, and will hide them from console output in builds. As a side effect of the fix for [SECURITY-698](https://www.jenkins.io/security/advisory/2018-02-05/#credentials-binding), `$` characters in secrets are escaped to `$$`. This will then be expanded to $ again once the secret is passed to (post) build steps. Credentials Binding Plugin 1.22 and earlier does not mask the escaped form of the secret (containing `$$`). This occurs for example in the \"Execute Maven top-level targets\" build step included
O3 Security · Impact-Aware SCA

Is GHSA-7ff8-qfwx-8gx5 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improper masking of some secrets in Jenkins Credentials…