Overview 7 matches · 3 protected · 2 exploited · 1 CISA KEV · 2 public PoC · 2 EPSS ≥ 0.5
Protected by Waratek
3
42.9%
Rule in development
0
0.0%
Mitigation candidate
1
14.3%
No exploit published
3
42.9%
blocked by ARMR today
3
42.9%
partly blocked
0
0.0%
not blocked
4
57.1%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
28.6%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
5
71.4%
split by
peak 2 / month
Oct 171
No exploit published1
High1
not blocked1
No public exploit1
Nov 170
Dec 170
Jan 181
No exploit published1
Medium1
not blocked1
No public exploit1
Feb 181
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
Mar 180
Apr 180
May 180
Jun 180
Jul 180
Aug 180
Sep 180
Oct 180
Nov 180
Dec 181
No exploit published1
High1
not blocked1
No public exploit1
Jan 191
Mitigation candidate1
High1
not blocked1
Exploited1
Feb 190
Mar 192
Protected by Waratek2
Critical2
blocked by ARMR today2
Exploited1
No public exploit1
Nov 17Jan 18Mar 18May 18Jul 18Sep 18Nov 18Jan 19Mar 19
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-1003041 | Critical | 2019-03-28 | Protected by Waratek | No public exploit | A sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin 2.64 and earlier allows attackers to invoke arbitrary constructors in sandboxed scripts. |
| CVE-2019-1003030 | Critical | 2019-03-08 | Protected by Waratek | Exploited | A sandbox bypass vulnerability exists in Jenkins Pipeline: Groovy Plugin 2.63 and earlier in pom.xml, src/main/java/org/jenkinsci/plugins/workflow/cps/CpsGroovyShell.java that allows attackers able to control pipeline scripts to execute arbitrary code on the Jenkins master JVM. |
| CVE-2019-1003001 | High | 2019-01-22 | Mitigation candidate | Exploited | A sandbox bypass vulnerability exists in Pipeline: Groovy Plugin 2.61 and earlier in src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition.java, src/main/java/org/jenkinsci/plugins/workflow/cps/CpsGroovyShellFactory.java that allows attackers with Overall/Read permission to provide a pipeline script to an HTTP endpoint that can result in arbitrary code execution on the Jenkins master JVM. |
| CVE-2018-1000866 | High | 2018-12-10 | No exploit published | No public exploit | A sandbox bypass vulnerability exists in Pipeline: Groovy Plugin 2.59 and earlier in groovy-sandbox/src/main/java/org/kohsuke/groovy/sandbox/SandboxTransformer.java, groovy-cps/lib/src/main/java/com/cloudbees/groovy/cps/SandboxCpsTransformer.java that allows attackers with Job/Configure permission, or unauthorized attackers with SCM commit privileges and corresponding pipelines based on Jenkinsfiles set up in Jenkins, to execute arbitrary code on the Jenkins master JVM |
| CVE-2018-1000058 | High | 2018-02-09 | Protected by Waratek | No public exploit | Jenkins Pipeline: Supporting APIs Plugin 2.17 and earlier have an arbitrary code execution due to incomplete sandbox protection: Methods related to Java deserialization like readResolve implemented in Pipeline scripts were not subject to sandbox protection, and could therefore execute arbitrary code. This could be exploited e.g. by regular Jenkins users with the permission to configure Pipelines in Jenkins, or by trusted committers to repositories containing Jenkinsfiles. |
| CVE-2018-1000015 | Medium | 2018-01-23 | No exploit published | No public exploit | On Jenkins instances with Authorize Project plugin, the authentication associated with a build may lack the Computer/Build permission on some agents. This did not prevent the execution of Pipeline `node` blocks on those agents due to incorrect permissions checks in Pipeline: Nodes and Processes plugin 2.17 and earlier. |
| CVE-2017-1000096 | High | 2017-10-05 | No exploit published | No public exploit | Arbitrary code execution due to incomplete sandbox protection: Constructors, instance variable initializers, and instance initializers in Pipeline scripts were not subject to sandbox protection, and could therefore execute arbitrary code. This could be exploited e.g. by regular Jenkins users with the permission to configure Pipelines in Jenkins, or by trusted committers to repositories containing Jenkinsfiles. |