LogstashApplication · Jenkins
CVE-2020-2143
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 Logstash Plugin 2.3.1 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 Logstash Plugin versions 2.3.1 and earlier transmits configured credentials in plain text as part of its global Jenkins configuration form submission, potentially exposing sensitive credentials through network interception or logs.
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
LogstashApplication
<= 2.3.1CVSS 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 Logstash plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Logstash' in the list of installed pluginsAffected if The Logstash plugin appears in the installed plugins list
-
Check the installed Logstash plugin versionIn the same plugin list, locate the Logstash plugin and note the version number displayed in the version columnAffected if The installed version is 2.3.1 or any version lower than 2.3.1
-
Verify if credentials are configured in Logstash settingsNavigate to Manage Jenkins > Configure System > locate the Logstash configuration section and inspect whether any authentication credentials (such as username/password, API key, or token) are filled in the configuration fieldsAffected if Credentials fields in the Logstash plugin configuration contain actual values (not empty)
-
Check for credential exposure in logs or network trafficReview Jenkins logs (var/log/jenkins/jenkins.log) and any network captures for plaintext credentials matching the configured Logstash credentialsAffected if Plaintext credentials matching the Logstash configuration appear in logs or network traffic
You are affected if the Logstash plugin version is 2.3.1 or lower AND credentials are configured in the plugin settings, as these conditions enable the plain text credential transmission vulnerability.
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 Logstash Plugin to a version that addresses this vulnerability; if immediate upgrading is not possible, avoid storing credentials in the plugin configuration and verify that network paths are secured.
Fix this in Logstash
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2143 — 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-2143 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