dbcve.org
Email ExtensionPlugin / extension · Jenkins

CVE-2018-1000176

MEDIUM · 6.5 CVSS v3.0 Published 2018-05-08
Fix available
A fix is available. Upgrade to after 2.61 or later.
See remediation →
71/100
Remediation priority · Elevated
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
An exposure of sensitive information vulnerability exists in Jenkins Email Extension Plugin 2.61 and older in src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/global.groovy and ExtendedEmailPublisherDescriptor.java that allows attackers with control of a Jenkins administrator's web browser (e.g. malicious extension) to retrieve the configured SMTP password.

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.61 and older exposes the configured SMTP password in the plugin's configuration pages (global.groovy and ExtendedEmailPublisherDescriptor.java). Attackers with control of a Jenkins administrator's web browser, such as through a malicious browser extension, can retrieve this sensitive credential.

MitigationUpgrade Jenkins Email Extension Plugin to version 2.62 or later which contains the fix for this vulnerability.

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

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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. Check if Jenkins Email Extension Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or check the plugin directory on the Jenkins master ($JENKINS_HOME/plugins/ for plugin files). Look for 'email-ext' in the list of installed plugins.
    Affected if The plugin is not installed or not present in the plugin list.
  2. Identify the installed version of the Email Extension Plugin
    In the Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and find the 'Email Extension Plugin' entry in the list. The version number is displayed in the 'Version' column. Alternatively, check the version file in the plugin directory: $JENKINS_HOME/plugins/email-ext/META-INF/MANIFEST.MF
    Affected if The version is 2.61 or lower.
  3. Verify if SMTP credentials are configured in Extended Email Publisher settings
    Navigate to Manage Jenkins > Configure System > Extended E-mail Notification section (or under the Email Extension plugin configuration). Check whether an SMTP password is specified in the 'SMTP Password' field.
    Affected if An SMTP password is configured in the plugin settings.
  4. Confirm the password is visible on the plugin configuration page
    As a Jenkins administrator, navigate to the Email Extension plugin configuration page (Manage Jenkins > Configure System > Extended E-mail Notification or the global.groovy configuration endpoint). Inspect whether the SMTP password field displays the configured password in plain text or is retrievable through the UI.
    Affected if The configured SMTP password is visible or accessible through the configuration UI.

Your environment is affected if the Email Extension Plugin version is 2.61 or earlier AND an SMTP password is configured, because the password will be exposed in the plugin configuration pages.

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
Upgrade available Upgrade to a release after 2.61
Interim mitigation

Upgrade Jenkins Email Extension Plugin to version 2.62 or later which contains the fix for this vulnerability.

Fix this in Email Extension Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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