Openshift DeployerApplication · Jenkins
CVE-2020-2155
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins OpenShift Deployer Plugin 1.2.0 and earlier transmits configured credentials in plain text as part of its global Jenkins configuration form, potentially resulting in their exposure.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins OpenShift Deployer Plugin versions 1.2.0 and earlier transmits configured credentials in plain text as part of the global Jenkins configuration form. This exposes credentials in the web interface, potentially allowing unauthorized users with access to view the configuration to obtain these credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Openshift DeployerApplication
<= 1.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify OpenShift Deployer Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'OpenShift Deployer' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn the Installed Plugins tab, locate OpenShift Deployer and note the Version column. Alternatively, check the plugin's POM or manifest file in the Jenkins plugin directoryAffected if The version is 1.2.0 or earlier
-
Confirm credentials are configured for the pluginNavigate to Jenkins > Manage Jenkins > Configure System and locate the OpenShift Deployer configuration section. Check if any OpenShift credentials are configured (username/password or secret tokens)Affected if Credentials fields contain values (not empty)
-
Inspect credential transmission in configuration formView the page source or use browser developer tools to examine the global configuration form HTML. Look for input fields containing plain text credentials in the OpenShift Deployer sectionAffected if Credentials appear as plain text values in the HTML form (not masked, not replaced with asterisks)
A user is affected if the OpenShift Deployer Plugin version 1.2.0 or earlier is installed AND credentials are configured in the plugin configuration, resulting in plain text credential exposure in the web interface.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the OpenShift Deployer Plugin to a version beyond 1.2.0 that addresses the plain text credential transmission. If an upgrade is unavailable, review who has access to the Jenkins global configuration and consider using Jenkins credential masking mechanisms.
Fix this in Openshift Deployer
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2155 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-2155 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data