Overview 3 matches · 2 protected
3matches
2protected66.7%
Protected by Waratek
3
100.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
blocked by ARMR today
2
66.7%
partly blocked
1
33.3%
not blocked
0
0.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
3
100.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 1 / month
Oct 171
Protected by Waratek1
High1
partly blocked1
Exploited1
Nov 170
Dec 170
Jan 180
Feb 180
Mar 180
Apr 180
May 180
Jun 180
Jul 180
Aug 181
Protected by Waratek1
High1
blocked by ARMR today1
Exploited1
Sep 180
Oct 180
Nov 180
Dec 180
Jan 190
Feb 190
Mar 191
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
Nov 17Jan 18Mar 18May 18Jul 18Sep 18Nov 18Jan 19Mar 19
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-2018-11776 | High | 2018-08-22 | Protected by Waratek | Exploited | Apache Struts versions 2.3 to 2.3.34 and 2.5 to 2.5.16 suffer from possible Remote Code Execution when alwaysSelectFullNamespace is true (either by user or a plugin like Convention Plugin) and then: results are used with no namespace and in same time, its upper package have no or wildcard namespace and similar to results, same possibility when using url tag which doesn't have value and action set and in same time, its upper package have no or wildcard namespace. |
| CVE-2017-12617 | High | 2017-10-04 | Protected by Waratek | Exploited | When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g. via setting the readonly initialisation parameter of the Default servlet to false) it was possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server. |