How severe is CVE-2020-2181?

CVE-2020-2181 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-2181?

CVE-2020-2181 affects the following packages: org.jenkins-ci.plugins:credentials-binding (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-2181?

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 CVE-2020-2181 is resolved across your whole dependency graph.

How do I detect CVE-2020-2181 in my Maven dependencies?

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.

How do I mitigate CVE-2020-2181 if there is no patch (or I can't update yet)?

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.

Is CVE-2020-2181 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-2181 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-2181?

CVE-2020-2181 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 66th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-2181?

CVE-2020-2181 is classified as CWE-522 (CWE-522). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-2181 published, and has it been updated?

CVE-2020-2181 was published on May 6, 2020 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2020-2181 — credentials-binding

MEDIUMFix: jenkinsci/credentials-binding-plugin@59ead11

CVE-2020-2181 is a medium-severity (CVSS 6.5) 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.

Secrets are not masked by Jenkins Credentials Binding Plugin in builds without build steps

Also known asGHSA-43j2-r4v3-m8jp

Published

May 6, 2020

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk+0.02%

Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk

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

Jenkins Credentials Binding Plugin 1.22 and earlier does not mask (i.e., replace with asterisks) secrets in the build log when the build contains no build steps.

Jenkins Credentials Binding Plugin 1.23 now masks secrets when the build contains no build steps.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:credentials-binding`	all versions	1.23`org.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

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.
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 CVE-2020-2181 is resolved across your whole dependency graph.
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 HatModerate

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 3.11	`atomic-enterprise-service-catalog-1:3.11.248-1.git.1.9aad2ef.el7`	RHBA-2020:2990
Red Hat OpenShift Container Platform 4.3	`jenkins-2-plugins-0:4.3.1601981312-1.el7`	RHSA-2020:4265
Red Hat OpenShift Container Platform 4.4	`jenkins-2-plugins-0:4.4.1598545590-1.el7`	RHSA-2020:3625
Red Hat OpenShift Container Platform 4.5	`jenkins-2-plugins-0:4.5.1596698303-1.el7`	RHSA-2020:3453

Frequently Asked Questions

Jenkins Credentials Binding Plugin 1.22 and earlier does not mask (i.e., replace with asterisks) secrets in the build log when the build contains no build steps. Jenkins Credentials Binding Plugin 1.23 now masks secrets when the build contains no build steps.

O3 Security · Impact-Aware SCA

Is CVE-2020-2181 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-522CWE-522

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

May 6, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2020-2181

GHSA-43j2-r4v3-m8jp

References

Advisoryopenwall.com Advisoryjenkins.io · 2020 05 06 Advisorynvd.nist.gov · CVE 2020 2181 Webgithub.com · 59ead11bcb3fd132258d1d7da4a34d47750f40d2 Packagegithub.com · credentials binding plugin

Related vulnerabilities

Also affects credentials-binding

This CVE is medium severity; 6 of 7 other CVEs affecting credentials-binding are rated as high or higher (top: high).

CVE-2026-48922CVE-2026-42520CVE-2025-53650CVE-2020-2182CVE-2019-1010241CVE-2018-1000057CVE-2022-20616

Same weakness: CWE-522

This CVE is medium severity; 1 of 1 other CVE with CWE-522 is rated as high or higher (top: critical).

CVE-2026-105769Browse all CWE-522

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2020-2181 — credentials-binding

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2020-2181 in your dependencies?