Overview 10 matches · 1 protected · 3 exploited · 1 CISA KEV · 4 public PoC · 4 EPSS ≥ 0.5
Protected by Waratek
2
20.0%
Rule in development
0
0.0%
Mitigation candidate
3
30.0%
No exploit published
5
50.0%
blocked by ARMR today
1
10.0%
partly blocked
1
10.0%
not blocked
8
80.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 4 / year
20101
Protected by Waratek1
Medium1
blocked by ARMR today1
Working exploit published1
20110
20120
20130
20140
20150
20162
Protected by Waratek1
No exploit published1
Critical1
High1
partly blocked1
not blocked1
Exploited1
No public exploit1
20170
20180
20191
No exploit published1
High1
not blocked1
No public exploit1
20204
Mitigation candidate2
No exploit published2
Critical3
High1
not blocked4
Exploited1
Proof of concept only1
No public exploit2
20212
Mitigation candidate1
No exploit published1
Critical2
not blocked2
Exploited1
Forecast only1
201020112012201320142015201620172018201920202021
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2021-41303 | Critical | 2021-09-17 | No exploit published | Forecast only | Apache Shiro before 1.8.0, when using Apache Shiro with Spring Boot, a specially crafted HTTP request may cause an authentication bypass. Users should update to Apache Shiro 1.8.0. |
| CVE-2020-17523 | Critical | 2021-02-03 | Mitigation candidate | Exploited | Apache Shiro before 1.7.1, when using Apache Shiro with Spring, a specially crafted HTTP request may cause an authentication bypass. |
| CVE-2020-17510 | Critical | 2020-11-05 | No exploit published | No public exploit | Apache Shiro before 1.7.0, when using Apache Shiro with Spring, a specially crafted HTTP request may cause an authentication bypass. |
| CVE-2020-13933 | High | 2020-08-17 | Mitigation candidate | Proof of concept only | Apache Shiro before 1.6.0, when using Apache Shiro, a specially crafted HTTP request may cause an authentication bypass. |
| CVE-2020-11989 | Critical | 2020-06-22 | No exploit published | No public exploit | Apache Shiro before 1.5.3, when using Apache Shiro with Spring dynamic controllers, a specially crafted request may cause an authentication bypass. |
| CVE-2020-1957 | Critical | 2020-03-25 | Mitigation candidate | Exploited | Apache Shiro before 1.5.2, when using Apache Shiro with Spring dynamic controllers, a specially crafted request may cause an authentication bypass. |
| CVE-2019-12422 | High | 2019-11-18 | No exploit published | No public exploit | Apache Shiro before 1.4.2, when using the default "remember me" configuration, cookies could be susceptible to a padding attack. |
| CVE-2016-6802 | High | 2016-09-20 | No exploit published | No public exploit | Apache Shiro before 1.3.2 allows attackers to bypass intended servlet filters and gain access by leveraging use of a non-root servlet context path. |
| CVE-2016-4437 | Critical | 2016-06-07 | Protected by Waratek | Exploited | Apache Shiro before 1.2.5, when a cipher key has not been configured for the "remember me" feature, allows remote attackers to execute arbitrary code or bypass intended access restrictions via an unspecified request parameter. |
| CVE-2010-3863 | Medium | 2010-11-05 | Protected by Waratek | Working exploit published | Apache Shiro before 1.1.0, and JSecurity 0.9.x, does not canonicalize URI paths before comparing them to entries in the shiro.ini file, which allows remote attackers to bypass intended access restrictions via a crafted request, as demonstrated by the /./account/index.jsp URI. |