Overview 14 matches · 1 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
1
7.1%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
13
92.9%
blocked by ARMR today
1
7.1%
partly blocked
0
0.0%
not blocked
13
92.9%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
14
100.0%
split by
peak 6 / quarter
Q1 171
No exploit published1
High1
not blocked1
No public exploit1
Q2 170
Q3 170
Q4 172
No exploit published2
High1
Medium1
not blocked2
No public exploit2
Q1 181
No exploit published1
Medium1
not blocked1
No public exploit1
Q2 180
Q3 180
Q4 181
No exploit published1
High1
not blocked1
No public exploit1
Q1 192
Protected by Waratek1
No exploit published1
Critical1
High1
blocked by ARMR today1
not blocked1
No public exploit2
Q2 190
Q3 196
No exploit published6
High2
Medium4
not blocked6
No public exploit6
Q4 191
No exploit published1
Critical1
not blocked1
No public exploit1
Q1 17Q2 17Q3 17Q4 17Q1 18Q2 18Q3 18Q4 18Q1 19Q2 19Q3 19Q4 19
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-10431 | Critical | 2019-10-01 | No exploit published | No public exploit | A sandbox bypass vulnerability in Jenkins Script Security Plugin 1.64 and earlier related to the handling of default parameter expressions in constructors allowed attackers to execute arbitrary code in sandboxed scripts. |
| CVE-2019-10400 | Medium | 2019-09-12 | No exploit published | No public exploit | A sandbox bypass vulnerability in Jenkins Script Security Plugin 1.62 and earlier related to the handling of subexpressions in increment and decrement expressions not involving actual assignment allowed attackers to execute arbitrary code in sandboxed scripts. |
| CVE-2019-10399 | Medium | 2019-09-12 | No exploit published | No public exploit | A sandbox bypass vulnerability in Jenkins Script Security Plugin 1.62 and earlier related to the handling of property names in property expressions in increment and decrement expressions allowed attackers to execute arbitrary code in sandboxed scripts. |
| CVE-2019-10394 | Medium | 2019-09-12 | No exploit published | No public exploit | A sandbox bypass vulnerability in Jenkins Script Security Plugin 1.62 and earlier related to the handling of property names in property expressions on the left-hand side of assignment expressions allowed attackers to execute arbitrary code in sandboxed scripts. |
| CVE-2019-10393 | Medium | 2019-09-12 | No exploit published | No public exploit | A sandbox bypass vulnerability in Jenkins Script Security Plugin 1.62 and earlier related to the handling of method names in method call expressions allowed attackers to execute arbitrary code in sandboxed scripts. |
| CVE-2019-10356 | High | 2019-07-31 | No exploit published | No public exploit | A sandbox bypass vulnerability in Jenkins Script Security Plugin 1.61 and earlier related to the handling of method pointer expressions allowed attackers to execute arbitrary code in sandboxed scripts. |
| CVE-2019-10355 | High | 2019-07-31 | No exploit published | No public exploit | A sandbox bypass vulnerability in Jenkins Script Security Plugin 1.61 and earlier related to the handling of type casts allowed attackers to execute arbitrary code in sandboxed scripts. |
| CVE-2019-1003040 | Critical | 2019-03-28 | Protected by Waratek | No public exploit | A sandbox bypass vulnerability in Jenkins Script Security Plugin 1.55 and earlier allows attackers to invoke arbitrary constructors in sandboxed scripts. |
| CVE-2019-1003024 | High | 2019-02-20 | No exploit published | No public exploit | A sandbox bypass vulnerability exists in Jenkins Script Security Plugin 1.52 and earlier in RejectASTTransformsCustomizer.java that allows attackers with Overall/Read permission to provide a Groovy script to an HTTP endpoint that can result in arbitrary code execution on the Jenkins master JVM. |
| CVE-2018-1000865 | High | 2018-12-10 | No exploit published | No public exploit | A sandbox bypass vulnerability exists in Script Security Plugin 1.47 and earlier in groovy-sandbox/src/main/java/org/kohsuke/groovy/sandbox/SandboxTransformer.java that allows attackers with Job/Configure permission to execute arbitrary code on the Jenkins master JVM, if plugins using the Groovy sandbox are installed. |
| CVE-2017-1000505 | Medium | 2018-01-25 | No exploit published | No public exploit | In Jenkins Script Security Plugin version 1.36 and earlier, users with the ability to configure sandboxed Groovy scripts are able to use a type coercion feature in Groovy to create new `File` objects from strings. This allowed reading arbitrary files on the Jenkins master file system. Such a type coercion is now subject to sandbox protection and considered to be a call to the `new File(String)` constructor for the purpose of in-process script approval. |
| CVE-2017-1000107 | High | 2017-10-05 | No exploit published | No public exploit | Script Security Plugin did not apply sandboxing restrictions to constructor invocations via positional arguments list, super constructor invocations, method references, and type coercion expressions. This could be used to invoke arbitrary constructors and methods, bypassing sandbox protection. |
| CVE-2017-1000095 | Medium | 2017-10-05 | No exploit published | No public exploit | The default whitelist included the following unsafe entries: DefaultGroovyMethods.putAt(Object, String, Object); DefaultGroovyMethods.getAt(Object, String). These allowed circumventing many of the access restrictions implemented in the script sandbox by using e.g. currentBuild['rawBuild'] rather than currentBuild.rawBuild. Additionally, the following entries allowed accessing private data that would not be accessible otherwise due to script security: groovy.json.JsonOutput.toJson(Closure); groovy.json.JsonOutput.toJson(Object). |
| CVE-2016-3102 | High | 2017-02-09 | No exploit published | No public exploit | The Script Security plugin before 1.18.1 in Jenkins might allow remote attackers to bypass a Groovy sandbox protection mechanism via a plugin that performs (1) direct field access or (2) get/set array operations. |