dbcve.org
Email ExtensionPlugin / extension · Jenkins

CVE-2019-1003032

CRITICAL · 9.9 CVSS v3.1 Published 2019-03-08
Fix available
A fix is available. Upgrade to after 2.64 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
A sandbox bypass vulnerability exists in Jenkins Email Extension Plugin 2.64 and earlier in pom.xml, src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java, src/main/java/hudson/plugins/emailext/plugins/content/EmailExtScript.java, src/main/java/hudson/plugins/emailext/plugins/content/ScriptContent.java, src/main/java/hudson/plugins/emailext/plugins/trigger/AbstractScriptTrigger.java that allows attackers with Job/Configure permission to execute arbitrary code on the Jenkins master JVM.

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

Jenkins Email Extension Plugin versions 2.64 and earlier contain a sandbox bypass vulnerability in multiple Java files (ExtendedEmailPublisher.java, EmailExtScript.java, ScriptContent.java, AbstractScriptTrigger.java) that allows attackers with Job/Configure permission to execute arbitrary code on the Jenkins master JVM through malicious script content in email trigger configurations.

MitigationUpgrade Jenkins Email Extension Plugin to version 2.65 or later. Until patched, restrict Job/Configure permission to trusted users only and review existing job configurations for suspicious email script content.

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.64

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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. Identify Email Extension Plugin version
    Navigate to Jenkins Manage Plugins page, locate the Email Extension plugin in the Installed tab, and note the version number displayed
    Affected if Version is 2.64 or earlier
  2. Confirm plugin is actively loaded
    Check the Jenkins script console or plugin manager for the Email Extension Plugin status to verify it is loaded and running
    Affected if Plugin is loaded and version 2.64 or earlier is reported
  3. Review user permissions for Job/Configure
    Navigate to Manage Jenkins > Manage Users and check which users or groups have the Job/Configure permission, or inspect overall authorization matrix settings
    Affected if Any untrusted or less-privileged users have Job/Configure permission
  4. Examine job email trigger configurations
    Open several jobs that use email triggers, go to Configure > Post-build Actions, and inspect any Editable Email Notification configurations for custom script content
    Affected if Any email trigger contains custom Groovy script content in the Advanced settings

A user is affected if the Email Extension Plugin version is 2.64 or earlier AND untrusted users have Job/Configure permission, regardless of whether malicious scripts are currently present in job configurations

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.64
Interim mitigation

Upgrade Jenkins Email Extension Plugin to version 2.65 or later. Until patched, restrict Job/Configure permission to trusted users only and review existing job configurations for suspicious email script content.

Recommended fix High confidence

Email Extension Plugin version 2.65 or later

  1. 1. In the Jenkins web UI, navigate to 'Manage Jenkins' > 'Manage Plugins'
  2. 2. Click on the 'Installed' tab
  3. 3. Locate the 'Email Extension Plugin' in the list of installed plugins
  4. 4. If version 2.64 or earlier is installed, click 'Update' to upgrade to the latest available version
  5. 5. After the update completes, restart Jenkins to apply the changes
  6. 6. Verify the plugin version has been updated to 2.65 or later via 'Manage Plugins' > 'Installed' tab
Caveat Review any email template or configuration changes that may be needed after upgrading, as minor version upgrades in Jenkins plugins can occasionally include behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Email Extension Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1003032 — 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-2019-1003032 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