Improper masking of some secrets in Jenkins Credentials Binding Plugin

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.1 · CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2020-2182: 0.90% estimated exploitation activity in the next 30 days; percentile 59.67 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

24 May 2022, 17:17 UTC

Last modified by the source

7 Dec 2023, 21:37 UTC

Source last checked

26 Oct 2026, 16:20 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7ff8-qfwx-8gx5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-2182

Advisory: Improper masking of some secrets in Jenkins Credentials Binding Plugin
IDs: CVE-2020-2182, GHSA-7ff8-qfwx-8gx5
Record: https://patchnext.com/advisories/cve-2020-2182 (revision 1, source checked 26 Oct 2026, 16:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins:credentials-binding 1.23. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:credentials-binding: affected <= 1.22; fixed in 1.23

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:credentials-binding: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.jenkins-ci.plugins:credentials-binding.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7ff8-qfwx-8gx5 (GitHub-reviewed advisory GHSA-7ff8-qfwx-8gx5 lists affected ranges: Maven org.jenkins-ci.plugins:credentials-binding >=0 <=1.22)

Commands are suggestions: review each one before running it.