# CVE-2020-2232: Jenkins Email Extension Plugin SMTP password transmitted and displayed in plain text

> The Jenkins Email Extension Plugin exposes SMTP passwords in plain text within the global configuration form, allowing attackers with access to view sensitive credentials.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5c4v-vh95-c67c

## What is CVE-2020-2232?

CVE-2020-2232 is a high-severity vulnerability in Jenkins Email Extension Plugin, published on 12 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2020-2232?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:email-ext. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:email-ext` | Maven | From 2.72 | 2.74 |
| `org.jenkins-ci.plugins:email-ext` | Maven | From 2.72 | 2.74 |

Products: Jenkins Email Extension.

## How do I fix CVE-2020-2232?

Upgrade org.jenkins-ci.plugins:email-ext to 2.74 or later.

## Is CVE-2020-2232 being exploited?

There is no known exploitation of CVE-2020-2232 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Email Extension Plugin

- [CVE-2023-25765](https://insights.sbomify.com/CVE-2023-25765/): Sandbox escape in Jenkins Email Extension Plugin (critical 9.9)
- [CVE-2019-1003032](https://insights.sbomify.com/CVE-2019-1003032/): Script security sandbox bypass in Jenkins Email Extension Plugin (critical 9.9)
- [CVE-2026-48920](https://insights.sbomify.com/CVE-2026-48920/): Jenkins Email Extension Plugin: Attackers able to control email content may specify `file:` URLs for images to read arbitrary files from Jenkins controller filesystem (high 8.8)
- [CVE-2018-1000176](https://insights.sbomify.com/CVE-2018-1000176/): Jenkins Email Extension Plugin showed plain text SMTP password in configuration form field (medium 6.5)
- [CVE-2023-25763](https://insights.sbomify.com/CVE-2023-25763/): Cross-site Scripting in Jenkins Email Extension Plugin (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-2232 and fix it if it is affected.

What it is: CVE-2020-2232 is a high-severity vulnerability in Jenkins Email Extension Plugin, published on 12 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-2232 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:email-ext (Maven): affected from 2.72; fixed in 2.74
- org.jenkins-ci.plugins:email-ext (Maven): affected from 2.72; fixed in 2.74

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-2232/ (Markdown: https://insights.sbomify.com/CVE-2020-2232/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-2232
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-2232
- OSV: https://osv.dev/vulnerability/CVE-2020-2232

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-2232/
Summaries are generated and may contain mistakes; the official description above is the record.