Jenkins Credentials Binding Plugin has Insufficiently Protected Credentials

Exploitation

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

CVSS

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

EPSS

• CVE-2018-1000057: 0.66% estimated exploitation activity in the next 30 days; percentile 51.77 (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.

Jenkins Credentials Binding plugin allows specifying passwords and other secrets as environment variables, and will hide them from console output in builds. However, since Jenkins will try to resolve references to other environment variables in environment variables passed to a build, this can result in values other than the one specified being provided to a build. For example, the value p4$$w0rd would result in Jenkins passing on p4$w0rd, as $$ is the escape sequence for a single $. Credentials Binding plugin does not prevent such a transformed value (e.g. p4$w0rd) from being shown on the build log, allowing users to reconstruct the actual password value from the transformed one. Credentials Binding plugin will now escape any $ characters in password values so they are correctly passed to the build. This issue did apply to freestyle and other classic job types, but does not apply to Pipelines.

Published by the source

13 May 2022, 01:48 UTC

Last modified by the source

28 Dec 2023, 18:43 UTC

Source last checked

26 Oct 2026, 16:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-38xm-xhvj-q2qf

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

# Patch Next advisory brief: CVE-2018-1000057

Advisory: Jenkins Credentials Binding Plugin has Insufficiently Protected Credentials
IDs: CVE-2018-1000057, GHSA-38xm-xhvj-q2qf
Record: https://patchnext.com/advisories/cve-2018-1000057 (revision 1, source checked 26 Oct 2026, 16:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
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.15. A vendor fix does not mean a deployment is fixed.

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

## 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-38xm-xhvj-q2qf (GitHub-reviewed advisory GHSA-38xm-xhvj-q2qf lists affected ranges: Maven org.jenkins-ci.plugins:credentials-binding >=0 <1.15)

Commands are suggestions: review each one before running it.