dbcve.org
Pipeline Remote LoaderApplication · Jenkins

CVE-2019-10328

CRITICAL · 9.9 CVSS v3.0 Published 2019-05-31
Fix available
A fix is available. Upgrade to after 1.4 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
Jenkins Pipeline Remote Loader Plugin 1.4 and earlier provided a custom whitelist for script security that allowed attackers to invoke arbitrary methods, bypassing typical sandbox protection.

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 Pipeline Remote Loader Plugin versions 1.4 and earlier contained an improperly configured custom whitelist for script security that allowed attackers to invoke arbitrary methods, effectively bypassing the Jenkins script sandbox protection and enabling remote code execution.

MitigationUpgrade the Jenkins Pipeline Remote Loader Plugin to version 1.5 or later, which addresses the overly permissive whitelist. After upgrading, verify that the script sandbox is properly enforcing restrictions and that legitimate pipeline functionality remains intact.

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
Pipeline Remote LoaderApplication
Affected:<= 1.4

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.0/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. Verify Pipeline Remote Loader Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Pipeline Remote Loader', or check the JENKINS_HOME/plugins directory for the pipeline-remote-loader plugin folder.
    Affected if The plugin is present in the installed plugins list.
  2. Determine the installed plugin version
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, find Pipeline Remote Loader, and note the version number shown in the plugin details.
    Affected if The version is 1.4 or earlier (versions 1.0 through 1.4 are affected).
  3. Check for active Pipeline Remote Loader usage
    Search Jenkins job configurations and Jenkinsfiles for references to 'pipelineRemoteLoader' or the step 'loadRemotePipeline', which are the plugin-specific steps that invoke the vulnerable whitelist.
    Affected if Any job or pipeline references the Pipeline Remote Loader steps, meaning the plugin feature is in use.
  4. Review custom script security whitelist configuration
    Check Jenkins configuration files under JENKINS_HOME for any script-security whitelist settings related to pipeline-remote-loader, or inspect the plugin's configuration through Manage Jenkins > Configure System if available.
    Affected if A custom whitelist is configured that permits methods beyond the standard sandbox restrictions.

You are affected if the Pipeline Remote Loader Plugin is installed with version 1.4 or earlier and the plugin functionality is being used, as the improperly configured whitelist allows sandbox bypass.

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

Upgrade the Jenkins Pipeline Remote Loader Plugin to version 1.5 or later, which addresses the overly permissive whitelist. After upgrading, verify that the script sandbox is properly enforcing restrictions and that legitimate pipeline functionality remains intact.

Recommended fix Moderate confidence

Pipeline Remote Loader version 1.5 or later

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate 'Pipeline Remote Loader' plugin in the list
  5. If the installed version is 1.4 or earlier, select the plugin and click 'Download now and install after restart'
  6. Alternatively, download the fixed version from the Jenkins plugin repository or Jenkins Update Center
  7. Restart Jenkins after the upgrade completes
  8. Verify the new version is installed by checking the plugin management page

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

Fix this in Pipeline Remote Loader 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-10328 — 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-10328 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