Is CVE-2019-1003030 exploited in the wild?

Yes. CVE-2019-1003030 is known to be exploited in the wild, first recorded on 25 March 2022. Treat it as urgent.

How severe is CVE-2019-1003030?

Critical severity, with a CVSS score of 3.1, published 13 May 2022.

Which products and versions are affected?

org.jenkins-ci.plugins.workflow:workflow-cps (Maven) ECOSYSTEM:introduced=0,fixed=2.64.

Is there a fix for CVE-2019-1003030?

Yes. org.jenkins-ci.plugins.workflow:workflow-cps (Maven): upgrade to 2.64 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2019-1003030 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2019-1003030?

Check whether you run Jenkins Matrix Project Plugin or org.jenkins-ci.plugins.workflow:workflow-cps (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.

CVE-2019-1003030: Sandbox bypass in Jenkins Pipeline: Groovy Plugin

CVE-2019-1003030 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2022-05-13

A sandbox bypass vulnerability in the Jenkins Pipeline: Groovy Plugin allows attackers who can control pipeline scripts to execute arbitrary code on the Jenkins master JVM. This occurs due to improper sandbox restrictions in CpsGroovyShell.java, leading to remote code execution.

Technologies: org.jenkins-ci.plugins.workflow:workflow-cps (Maven). Vendors: Jenkins, Maven.

Quick answers

Is CVE-2019-1003030 exploited in the wild?: Yes. CVE-2019-1003030 is known to be exploited in the wild, first recorded on 25 March 2022. Treat it as urgent.
How severe is CVE-2019-1003030?: Critical severity, with a CVSS score of 3.1, published 13 May 2022.
Which products and versions are affected?: org.jenkins-ci.plugins.workflow:workflow-cps (Maven) ECOSYSTEM:introduced=0,fixed=2.64.
Is there a fix for CVE-2019-1003030?: Yes. org.jenkins-ci.plugins.workflow:workflow-cps (Maven): upgrade to 2.64 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2019-1003030 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2019-1003030?: Check whether you run Jenkins Matrix Project Plugin or org.jenkins-ci.plugins.workflow:workflow-cps (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.workflow:workflow-cps (Maven): upgrade to 2.64 or later

# set org.jenkins-ci.plugins.workflow:workflow-cps to 2.64 in your pom.xml or build.gradle

Affected products

Jenkins Pipeline: Groovy Plugin 2.63 and earlier
Jenkins Matrix Project Plugin (none specified)

Identifiers

CVE-2019-1003030
GHSA-r6mc-mrvr-23cr

Timeline

2019-03-06: advisory: Vendor security advisory published by Jenkins.
2019-03-12: disclosed: Initial NVD analysis.
2022-03-25: kev added: Added to CISA Known Exploited Vulnerabilities Catalog.

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.