S3 PublisherApplication · Jenkins
CVE-2020-2114
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 S3 publisher Plugin 0.11.4 and earlier transmits configured credentials in plain text as part of the 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 S3 publisher Plugin version 0.11.4 and earlier transmits AWS credentials in plain text as part of the global Jenkins configuration form submission, allowing potential exposure of sensitive access keys and secret keys through network interception or log files.
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
S3 PublisherApplication
<= 0.11.4CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Identify S3 Publisher plugin installation and versionNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'S3 Publisher' or 's3', or use the CLI: jenkins-cli.jar or REST API: /pluginManager/plugin/s3-publisher/api/json?pretty=trueAffected if The plugin is installed and the version is 0.11.4 or lower
-
Determine if AWS credentials are configuredNavigate to Jenkins > Configure System > look for the 'Amazon S3 profiles' or 'S3 Publisher' section, or inspect the configuration XML at $JENKINS_HOME/org.jenkinsci.plugins.s3publish.S3Publisher.xml for credential entriesAffected if AWS Access Key ID and Secret Access Key fields contain values (even if masked, they are stored/transmitted in plain text in vulnerable versions)
-
Inspect Jenkins logs for credential exposureReview Jenkins logs (typically at $JENKINS_HOME/logs/ or the log console output) for entries containing 'AKIA' (common AWS access key prefix) or looking for any plain text AWS key patterns submitted during configuration savesAffected if Log files contain plain text AWS access keys or secret keys from configuration form submissions
-
Check configuration backup filesReview any configuration backup files, XML configuration exports, or old configuration snapshots in $JENKINS_HOME/ for XML files that may contain S3 publisher configuration with stored credentialsAffected if Backup or exported configuration files contain unencrypted AWS credentials in plain text
User is affected if the S3 Publisher plugin version is 0.11.4 or lower AND AWS credentials are configured in the plugin, with additional risk if logs or configuration files show plain text credential exposure.
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 S3 publisher Plugin to a version newer than 0.11.4 which addresses the plain text credential transmission. After upgrading, rotate the exposed AWS credentials as a precaution.
Fix this in S3 Publisher
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2114 — 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-2114 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