dbcve.org
Email ExtensionPlugin / extension · Jenkins

CVE-2020-2232

HIGH · 7.5 CVSS v3.1 Published 2020-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Jenkins Email Extension Plugin 2.72 and 2.73 transmits and displays the SMTP password in plain text as part of the global Jenkins configuration form, potentially resulting in its 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 confidence

The Jenkins Email Extension Plugin versions 2.72 and 2.73 has a vulnerability where the SMTP password is transmitted and displayed in plain text within the global Jenkins configuration form instead of being masked or handled securely, potentially exposing credentials to unauthorized parties.

MitigationUpdate the Email Extension Plugin to version 2.74 or later where this issue is resolved, and consider rotating the SMTP password as it may have been exposed.

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
Email ExtensionPlugin / extension
Affected:= 2.72= 2.73

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Email Extension Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Email Extension' in the list of installed plugins.
    Affected if The Email Extension Plugin is listed as installed.
  2. Check the installed plugin version
    In the Manage Plugins > Installed tab, find the Email Extension Plugin and note the version number displayed in the Version column.
    Affected if The version is exactly 2.72 or 2.73.
  3. Inspect SMTP password field in global configuration
    Go to Manage Jenkins > Configure System > locate the 'Extended E-mail Notification' section (or E-mail Notification section) and examine the SMTP password field. Check whether the password characters are visible as plain text or properly masked with dots/asterisks.
    Affected if The SMTP password field displays the password in plain text characters rather than being masked.

The environment is affected if the Email Extension Plugin version is 2.72 or 2.73 AND the SMTP password field in the global Jenkins configuration shows the password in plain text.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Email Extension Plugin to version 2.74 or later where this issue is resolved, and consider rotating the SMTP password as it may have been exposed.

Fix this in Email Extension Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA0.5 h
4.5 hours of engineering $800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,280.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2232 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-2232 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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