How severe is GHSA-5c4v-vh95-c67c?

GHSA-5c4v-vh95-c67c has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-5c4v-vh95-c67c?

GHSA-5c4v-vh95-c67c affects the following packages: org.jenkins-ci.plugins:email-ext (Maven). Ecosystems affected: Maven.

How do I fix GHSA-5c4v-vh95-c67c?

Update org.jenkins-ci.plugins:email-ext to 2.74 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5c4v-vh95-c67c is resolved across your whole dependency graph.

How do I detect GHSA-5c4v-vh95-c67c in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:email-ext. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-5c4v-vh95-c67c if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-5c4v-vh95-c67c?

O3 pinpoints whether GHSA-5c4v-vh95-c67c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-5c4v-vh95-c67c actively exploited in the wild?

No public exploit code has been indexed for GHSA-5c4v-vh95-c67c yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-5c4v-vh95-c67c?

GHSA-5c4v-vh95-c67c is classified as CWE-319 (CWE-319). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-5c4v-vh95-c67c published, and has it been updated?

GHSA-5c4v-vh95-c67c was published on May 24, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-5c4v-vh95-c67c

LOWFix: jenkinsci/email-ext-plugin@b51497d

GHSA-5c4v-vh95-c67c is a low-severity (CVSS 3.7) CWE-319 vulnerability in org.jenkins-ci.plugins:email-ext. O3 Security confirms whether GHSA-5c4v-vh95-c67c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Jenkins Email Extension Plugin SMTP password transmitted and displayed in plain text

Also known asCVE-2020-2232

Published

May 24, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:email-ext

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Email Extension Plugin stores an SMTP password in its global configuration file hudson.plugins.emailext.ExtendedEmailPublisher.xml on the Jenkins controller as part of its configuration.

While this password is stored encrypted on disk, it is transmitted and displayed in plain text as part of the configuration form by Email Extension Plugin 2.72 and 2.73. This can result in exposure of the password.

Email Extension Plugin 2.74 transmits the SMTP password in its global configuration encrypted and masks it using a password field.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:email-ext`	≥ 2.72&&< 2.74	2.74

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:email-ext. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.jenkins-ci.plugins:email-ext to 2.74 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5c4v-vh95-c67c is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-5c4v-vh95-c67c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5c4v-vh95-c67c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Email Extension Plugin stores an SMTP password in its global configuration file `hudson.plugins.emailext.ExtendedEmailPublisher.xml` on the Jenkins controller as part of its configuration. While this password is stored encrypted on disk, it is transmitted and displayed in plain text as part of the configuration form by Email Extension Plugin 2.72 and 2.73. This can result in exposure of the password. Email Extension Plugin 2.74 transmits the SMTP password in its global configuration encrypted and masks it using a password field.

O3 Security · Impact-Aware SCA

Is GHSA-5c4v-vh95-c67c in your dependencies?

O3 detects GHSA-5c4v-vh95-c67c across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works