Email ExtensionPlugin / extension · Jenkins
CVE-2017-2654
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-email-ext before version 2.57.1 is vulnerable to an Information Exposure. The Email Extension Plugins is able to send emails to a dynamically created list of users based on the changelogs, like authors of SCM changes since the last successful build. This could in some cases result in emails being sent to people who have no user account in Jenkins, and in rare cases even people who were not involved in whatever project was being built, due to some mapping based on the local-part of email addresses.
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 Email Extension Plugin determines email recipients by extracting SCM changelog authors and mapping them to email addresses. The vulnerability exists because the plugin uses only the local-part (username portion before @) of email addresses for mapping, which can incorrectly match against unrelated users or send emails to non-existent accounts.
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
< 2.57.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.0/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.
-
Locate the Email Extension Plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and find the 'Email Extension' plugin. Note the version number displayed.Affected if The installed version is earlier than 2.57.1 (for example, 2.57.0, 2.56, or earlier)
-
Verify Email Extension is configured at system levelGo to Manage Jenkins > Configure System > Extended Email Notification section. Check if the plugin is configured with an SMTP server and default recipients.Affected if The Extended Email Notification section is configured and enabled in Jenkins system settings
-
Identify jobs using Email Extension with SCM triggersReview job configurations: check each job's Post-build Actions for 'Editable Email Notification' or 'Email-ext' triggers, particularly looking for 'Change Log' or 'SCM' related recipient triggers.Affected if Jobs are configured to send emails based on SCM changelog authors or change log contributors
-
Check recipient mapping behaviorExamine the email recipients generated for a recent build with SCM changes. Verify whether emails are being sent to addresses derived only from usernames (local-part before @).Affected if Emails are being sent to recipients derived from SCM author usernames without full address validation
Your environment is affected if the Email Extension Plugin version is below 2.57.1 and jobs are configured to send emails based on SCM changelog authors.
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 data2.57.1
Upgrade jenkins-email-ext plugin to version 2.57.1 or later to address the flawed email recipient mapping logic.
Fix this in Email Extension
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2654 — 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-2017-2654 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