Overview 108 matches · 13 protected · 3 exploited · 1 CISA KEV · 5 public PoC · 6 EPSS ≥ 0.5
Protected by Waratek
13
12.0%
Rule in development
0
0.0%
Mitigation candidate
2
1.9%
No exploit published
93
86.1%
blocked by ARMR today
13
12.0%
partly blocked
0
0.0%
not blocked
95
88.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 15 / quarter
Q1 211
No exploit published1
Medium1
not blocked1
Forecast only1
Q2 218
Protected by Waratek2
Mitigation candidate1
No exploit published5
High1
Medium5
Low2
blocked by ARMR today2
not blocked6
Exploited1
Working exploit published2
Forecast only1
No public exploit4
Q3 211
Protected by Waratek1
Medium1
blocked by ARMR today1
Exploited1
Q4 211
No exploit published1
Critical1
not blocked1
No public exploit1
Q1 222
Protected by Waratek1
No exploit published1
Medium2
blocked by ARMR today1
not blocked1
No public exploit2
Q2 221
No exploit published1
Medium1
not blocked1
No public exploit1
Q3 227
Protected by Waratek2
No exploit published5
Critical1
High4
Medium1
Low1
blocked by ARMR today2
not blocked5
No public exploit7
Q4 223
No exploit published3
High1
Medium2
not blocked3
No public exploit3
Q1 233
Protected by Waratek2
No exploit published1
High2
Medium1
blocked by ARMR today2
not blocked1
Proof of concept only1
No public exploit2
Q2 234
No exploit published4
Critical1
Medium3
not blocked4
No public exploit4
Q3 235
Protected by Waratek1
No exploit published4
Critical1
High1
Medium2
Low1
blocked by ARMR today1
not blocked4
No public exploit5
Q4 236
Protected by Waratek1
Mitigation candidate1
No exploit published4
Critical1
High3
Medium2
blocked by ARMR today1
not blocked5
Exploited1
Proof of concept only1
No public exploit4
Q1 241
No exploit published1
High1
not blocked1
Proof of concept only1
Q2 244
No exploit published4
High2
Medium2
not blocked4
No public exploit4
Q3 245
No exploit published5
High1
Medium4
not blocked5
Proof of concept only1
No public exploit4
Q4 245
No exploit published5
High1
Medium4
not blocked5
Proof of concept only1
No public exploit4
Q1 250
Q2 254
Protected by Waratek1
No exploit published3
High3
Medium1
blocked by ARMR today1
not blocked3
Proof of concept only1
No public exploit3
Q3 258
No exploit published8
High2
Medium6
not blocked8
No public exploit8
Q4 253
No exploit published3
Critical1
Medium1
Low1
not blocked3
Proof of concept only2
No public exploit1
Q1 263
No exploit published3
High1
Medium2
not blocked3
Proof of concept only1
No public exploit2
Q2 266
No exploit published6
Critical3
High2
Medium1
not blocked6
Proof of concept only3
No public exploit3
Q3 2612
Protected by Waratek1
No exploit published11
Critical1
High5
Medium6
blocked by ARMR today1
not blocked11
Proof of concept only1
No public exploit11
Q4 2615
Protected by Waratek1
No exploit published14
Critical1
High13
Medium1
blocked by ARMR today1
not blocked14
No public exploit15
Q2 21Q4 21Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2021-28169 | Medium | 2021-06-09 | Mitigation candidate | Exploited | For Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to access protected resources within the WEB-INF directory. For example a request to `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application. |
| CVE-2020-6950 | Medium | 2021-06-02 | Protected by Waratek | Working exploit published | Directory traversal in Eclipse Mojarra before 2.3.14 allows attackers to read arbitrary files via the loc parameter or con parameter. |
| CVE-2021-28170 | Medium | 2021-05-26 | No exploit published | No public exploit | In the Jakarta Expression Language implementation 3.0.3 and earlier, a bug in the ELParserTokenManager enables invalid EL expressions to be evaluated as if they were valid. |
| CVE-2021-28168 | Medium | 2021-04-22 | No exploit published | No public exploit | Eclipse Jersey 2.28 to 2.33 and Eclipse Jersey 3.0.0 to 3.0.1 contains a local information disclosure vulnerability. This is due to the use of the File.createTempFile which creates a file inside of the system temporary directory with the permissions: -rw-r--r--. Thus the contents of this file are viewable by all other users locally on the system. As such, if the contents written is security sensitive, it can be disclosed to other local users. |
| CVE-2021-28165 | High | 2021-04-01 | No exploit published | Forecast only | In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame. |
| CVE-2021-28164 | Medium | 2021-04-01 | Protected by Waratek | Working exploit published | In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segments to access protected resources within the WEB-INF directory. For example a request to /context/%2e/WEB-INF/web.xml can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application. |
| CVE-2021-28163 | Low | 2021-04-01 | No exploit published | No public exploit | In Eclipse Jetty 9.4.32 to 9.4.38, 10.0.0.beta2 to 10.0.1, and 11.0.0.beta2 to 11.0.1, if a user uses a webapps directory that is a symlink, the contents of the webapps directory is deployed as a static webapp, inadvertently serving the webapps themselves and anything else that might be in that directory. |
| CVE-2020-27223 | Medium | 2021-02-26 | No exploit published | Forecast only | In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality” (i.e. q) parameters, the server may enter a denial of service (DoS) state due to high CPU usage processing those quality values, resulting in minutes of CPU time exhausted processing those quality values. |