dbcve.org
OntrackApplication · Jenkins

CVE-2019-10306

CRITICAL · 9.9 CVSS v3.1 Published 2019-04-18
Fix available
A fix is available. Upgrade to after 3.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
A sandbox bypass vulnerability in Jenkins ontrack Plugin 3.4 and earlier allowed attackers with control over ontrack 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 ontrack Plugin 3.4 and earlier allows attackers with control over ontrack DSL definitions to execute arbitrary code on the Jenkins master JVM, achieving full compromise of the Jenkins controller.

MitigationUpgrade the ontrack plugin to a version newer than 3.4. Additionally, restrict or audit who can create/modify ontrack DSL definitions in Jenkins jobs until the patch is applied.

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
OntrackApplication
Affected:<= 3.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.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 installed Ontrack plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or inspect the plugin file metadata in $JENKINS_HOME/plugins/ontrack/WEB-INF/MANIFEST.MF for the Plugin-Version attribute
    Affected if The plugin version is 3.4 or earlier
  2. Confirm Ontrack plugin is active
    Navigate to Jenkins > Manage Jenkins > Configure System and look for the Ontrack configuration section, or check if ontrack appears in the installed plugins list with status 'Enabled'
    Affected if The Ontrack plugin is installed and enabled in Jenkins
  3. Identify users or roles with DSL build step access
    Review Jenkins job configurations that use Ontrack DSL build steps (look for 'ontrack' in job DSL or Pipeline steps), and check who can configure these jobs via Matrix Authorization Strategy or Project-based Matrix Authorization
    Affected if Users other than administrators can create or modify jobs containing Ontrack DSL definitions
  4. Check for unrestricted script execution permissions
    Navigate to Manage Jenkins > Manage and Assign Roles > Manage Roles, and verify if any role grants Script Console access or sandbox bypass permissions beyond administrators
    Affected if Non-admin users have Script Console access or script approval rights that could bypass sandbox restrictions

You are affected if the Ontrack plugin version is 3.4 or earlier AND untrusted users have the ability to create or modify Ontrack DSL definitions in Jenkins jobs.

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

Upgrade the ontrack plugin to a version newer than 3.4. Additionally, restrict or audit who can create/modify ontrack DSL definitions in Jenkins jobs until the patch is applied.

Recommended fix Moderate confidence

ontrack plugin version > 3.4 (latest available version)

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Select the 'Installed' tab
  4. 4. Locate the ontrack plugin in the list
  5. 5. If update is available, click 'Update now' to upgrade to the latest version
  6. 6. Restart Jenkins to apply the update
  7. 7. Verify the plugin version is greater than 3.4 after update

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

Fix this in Ontrack Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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