Matrix ProjectApplication · Jenkins
CVE-2019-1003031
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 · uneditedA sandbox bypass vulnerability exists in Jenkins Matrix Project Plugin 1.13 and earlier in pom.xml, src/main/java/hudson/matrix/FilterScript.java that allows attackers with Job/Configure permission 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 confidenceA sandbox bypass vulnerability in Jenkins Matrix Project Plugin 1.13 and earlier allows authenticated attackers with Job/Configure permission to execute arbitrary code on the Jenkins master JVM by exploiting FilterScript.java, completely bypassing the script security sandbox.
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
Matrix ProjectApplication
<= 1.13
Openshift Container PlatformApplication
= 3.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Matrix Project Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'Matrix Project' or check the plugin version in the plugin's details panelAffected if Plugin is installed and version is 1.13 or earlier
-
Confirm the exact plugin versionIn the Installed Plugins tab, locate Matrix Project Plugin and note the Version column; compare against affected range <= 1.13Affected if Version displayed is 1.13 or lower
-
Identify users with Job/Configure permissionReview Jenkins authorization matrix at Manage Jenkins > Configure Global Security > Authorization, or check individual project configurations under Job > Configure > Matrix-based Security for granted permissionsAffected if Any user or group other than administrators has Job/Configure permission enabled
-
Detect active matrix projects using FilterScriptBrowse to each Jenkins job that uses the Matrix Project configuration and inspect whether FilterScript is defined in the Build section > Matrix Configuration or via the Groovy sandbox featureAffected if A matrix project exists with FilterScript configured and the plugin version is <= 1.13
If the Matrix Project Plugin version is 1.13 or earlier AND untrusted users have Job/Configure permission, the environment is vulnerable to remote code execution via sandbox bypass.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Matrix Project Plugin to version newer than 1.13. Until patched, restrict Job/Configure permission to only trusted users and consider disabling matrix project functionality if not required.
Matrix Project Plugin version 1.14 or later
- Upgrade Jenkins Matrix Project Plugin from version 1.13 or earlier to version 1.14 or later
- Navigate to Jenkins > Manage Jenkins > Manage Plugins > Updates
- Locate Matrix Project Plugin in the updates list and install the latest version
- Restart Jenkins to apply the plugin update
- For OpenShift Container Platform 3.11, ensure the underlying Jenkins instance has the updated plugin installed
- Verify the upgrade by checking the plugin version in Manage Plugins > Installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Matrix Project
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003031 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-1003031 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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