# CVE-2019-1003001: Jenkins Groovy Plugin sandbox bypass vulnerability

Source: https://junglewise.ai/threats/cve-2019-1003001-jenkins-groovy-plugin-sandbox-bypass-vulnerability  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2022-05-13  
License: CC BY 4.0 with a link back

CVE-2019-1003001 · Severity: low · CVSS 3.1 · Published 2022-05-13

Jenkins Groovy Plugin sandbox bypass vulnerability

Technologies: [org.jenkins-ci.plugins:script-security (Maven)](https://junglewise.ai/threats/technologies/org-jenkins-ci-plugins-script-security). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2019-1003001 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2019-1003001 being exploited in the wild.

**How severe is CVE-2019-1003001?** Low severity, with a CVSS score of 3.1, published 13 May 2022.

**Which products and versions are affected?** org.jenkins-ci.plugins:pipeline-model-definition (Maven) ECOSYSTEM:introduced=0,fixed=1.3.4.1; org.jenkins-ci.plugins:script-security (Maven) ECOSYSTEM:introduced=0,fixed=1.50; org.jenkins-ci.plugins.workflow:workflow-cps-parent (Maven) ECOSYSTEM:introduced=0,fixed=2.61.1.

**Is there a fix for CVE-2019-1003001?** Yes. org.jenkins-ci.plugins:pipeline-model-definition (Maven): upgrade to 1.3.4.1 or later; org.jenkins-ci.plugins:script-security (Maven): upgrade to 1.50 or later; org.jenkins-ci.plugins.workflow:workflow-cps-parent (Maven): upgrade to 2.61.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2019-1003001?** Check whether you run org.jenkins-ci.plugins:pipeline-model-definition (Maven), org.jenkins-ci.plugins:script-security (Maven) or org.jenkins-ci.plugins.workflow:workflow-cps-parent (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.jenkins-ci.plugins:pipeline-model-definition (Maven): upgrade to 1.3.4.1 or later

  ```sh
  # set org.jenkins-ci.plugins:pipeline-model-definition to 1.3.4.1 in your pom.xml or build.gradle
  ```

- org.jenkins-ci.plugins:script-security (Maven): upgrade to 1.50 or later

  ```sh
  # set org.jenkins-ci.plugins:script-security to 1.50 in your pom.xml or build.gradle
  ```

- org.jenkins-ci.plugins.workflow:workflow-cps-parent (Maven): upgrade to 2.61.1 or later

  ```sh
  # set org.jenkins-ci.plugins.workflow:workflow-cps-parent to 2.61.1 in your pom.xml or build.gradle
  ```


## Affected products

- org.jenkins-ci.plugins:pipeline-model-definition (Maven) ECOSYSTEM:introduced=0,fixed=1.3.4.1
- org.jenkins-ci.plugins:script-security (Maven) ECOSYSTEM:introduced=0,fixed=1.50
- org.jenkins-ci.plugins.workflow:workflow-cps-parent (Maven) ECOSYSTEM:introduced=0,fixed=2.61.1

## Identifiers

- CVE-2019-1003001
- GHSA-6q78-6xvr-26fg

## Related threats

- [Jenkins Script Security Plugin sandbox bypass via Groovy AST annotations](https://junglewise.ai/threats/cve-2026-57281-jenkins-script-security-plugin-sandbox-bypass-via-groovy-ast)
- [Jenkins Script Security Plugin sandbox bypass via Groovy implicit type casts](https://junglewise.ai/threats/cve-2026-57280-jenkins-script-security-plugin-sandbox-bypass-via-groovy-implicit)
- [Jenkins Script Security Plugin: Missing permission checks allow enumeration of pending and approved classpaths](https://junglewise.ai/threats/cve-2026-42519-jenkins-script-security-plugin-missing-permission-checks-allow)
- [Missing permission check in Jenkins Script Security Plugin](https://junglewise.ai/threats/cve-2024-52549-missing-permission-check-in-jenkins-script-security-plugin)
- [Jenkins Script Security Plugin sandbox bypass vulnerability](https://junglewise.ai/threats/cve-2024-34145-jenkins-script-security-plugin-sandbox-bypass-vulnerability)
