dbcve.org
Job DslApplication · Jenkins

CVE-2019-1003034

CRITICAL · 9.9 CVSS v3.1 Published 2019-03-08
Fix available
A fix is available. Upgrade to after 1.71 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 Job DSL Plugin 1.71 and earlier in job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/AbstractDslScriptLoader.groovy, job-dsl-plugin/build.gradle, job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JobDslWhitelist.groovy, job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/SandboxDslScriptLoader.groovy that allows attackers with control over Job DSL definitions 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

A sandbox bypass vulnerability in Jenkins Job DSL Plugin 1.71 and earlier allows attackers with control over Job DSL script definitions to execute arbitrary code on the Jenkins master JVM by circumventing Groovy sandbox security restrictions in AbstractDslScriptLoader.groovy, JobDslWhitelist.groovy, and SandboxDslScriptLoader.groovy.

MitigationUpgrade Jenkins Job DSL Plugin to version 1.72 or later. Until upgraded, restrict Job DSL script creation/modification permissions to trusted users only and audit existing DSL scripts for malicious 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
Job DslApplication
Affected:<= 1.71
Openshift Container PlatformApplication
Affected:= 3.11

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 Jenkins Job DSL Plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Job DSL' plugin, or run: jenkins-cli.jar who-am-i (or check $JENKINS_HOME/plugins/job-dsl.jpi/META-INF/MANIFEST.MF)
    Affected if The installed version is 1.71 or earlier
  2. Confirm plugin is actively used
    Check if any jobs reference Job DSL scripts by viewing job configurations, or search $JENKINS_HOME/jobs/ for files containing 'dsl' script definitions in the job config.xml files
    Affected if Jobs are configured to use Job DSL scripts with the vulnerable plugin version
  3. Check OpenShift Container Platform version (if applicable)
    For OpenShift Container Platform users: run 'oc version' or check the OCP version in the web console under Help > About, as OCP 3.11 ships with the vulnerable Jenkins plugin
    Affected if OCP version is exactly 3.11 and Jenkins with Job DSL plugin is enabled
  4. Verify sandbox protection status
    Review the Jenkins script approval configuration at $JENKINS_HOME/scriptApproval.xml or via Manage Jenkins > In-Process Script Approval to check if Groovy sandbox is enforced
    Affected if Groovy sandbox is enabled but users with Job DSL permission can still define custom Groovy scripts

You are affected if the Jenkins Job DSL Plugin version is 1.71 or earlier (or OCP 3.11 is running with bundled Jenkins) and Job DSL scripts are being processed by the Jenkins master.

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.71
Interim mitigation

Upgrade Jenkins Job DSL Plugin to version 1.72 or later. Until upgraded, restrict Job DSL script creation/modification permissions to trusted users only and audit existing DSL scripts for malicious content.

Recommended fix High confidence

Job DSL Plugin version 1.72

  1. 1. Navigate to Manage Jenkins > Manage Plugins > Updates tab
  2. 2. Locate the Job DSL plugin in the list of available updates
  3. 3. Select the plugin and click 'Download now and install after restart'
  4. 4. Wait for the plugin to update to version 1.72 or later
  5. 5. Restart Jenkins to complete the installation
  6. 6. Verify the installed version under Manage Jenkins > Manage Plugins > Installed tab
Caveat Review Job DSL scripts for compatibility with new sandbox restrictions

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

Fix this in Job Dsl Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,100
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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