dbcve.org
Mashup PortletsApplication · Jenkins

CVE-2019-10347

HIGH · 8.8 CVSS v3.1 Published 2019-07-11
Fix available
A fix is available. Upgrade to after 1.0.9 or later.
See remediation →
94/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
Jenkins Mashup Portlets Plugin stored credentials unencrypted on the Jenkins master where they can be viewed by users with access to the master file system.

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 Mashup Portlets Plugin stores credentials in plaintext (unencrypted) on the Jenkins master file system. Any user with file system access to the Jenkins master can read these stored credentials directly from disk, enabling credential theft and unauthorized access to integrated systems.

MitigationUpdate the Mashup Portlets Plugin to a patched version that uses Jenkins' built-in credential storage API, or remove stored credentials from the plugin if no update is available. Additionally, restrict physical and filesystem access to the Jenkins master server.

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
Mashup PortletsApplication
Affected:<= 1.0.9

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Verify Mashup Portlets plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed, or check the $JENKINS_HOME/plugins directory for a folder named mashup-portlets or similar. Use the Jenkins script console to run: Jenkins.instance.pluginManager.plugins.findAll { it.shortName == 'mashup-portlets' }
    Affected if The plugin is installed and its version is 1.0.9 or lower
  2. Locate the plugin configuration directory
    Check $JENKINS_HOME/mashup-portlets/ or $JENKINS_HOME/plugins/mashup-portlets/ for configuration files. Also check $JENKINS_HOME/org.jenkinsci.plugins.mashupportlets if it exists.
    Affected if The plugin directory exists and contains configuration XML files
  3. Inspect plugin configuration for stored credentials
    Examine any XML or properties files in the plugin directory for credential-related fields such as password, secret, token, apiKey, or similar. Open configuration files in a text editor and search for these keywords.
    Affected if Configuration files contain plaintext values in fields like password, secret, credentials, or apiKey
  4. Check for credential storage files
    Search the $JENKINS_HOME directory for files that may contain stored credentials from this plugin. Use: find $JENKINS_HOME -name '*mashup*' -type f to locate plugin-related files, then examine them for plaintext secrets.
    Affected if Any file contains plaintext credential strings associated with the Mashup Portlets plugin
  5. Review job or view configurations using the plugin
    Check $JENKINS_HOME/jobs/*/config.xml and any view configurations that may reference the Mashup Portlets plugin for embedded credential data.
    Affected if Job or view XML configurations contain plaintext credentials used by this plugin

You are affected if the Mashup Portlets plugin version 1.0.9 or lower is installed and any configuration files contain plaintext credentials that could be read from disk by an attacker with filesystem access.

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 1.0.9
Interim mitigation

Update the Mashup Portlets Plugin to a patched version that uses Jenkins' built-in credential storage API, or remove stored credentials from the plugin if no update is available. Additionally, restrict physical and filesystem access to the Jenkins master server.

Fix this in Mashup Portlets Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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