Overview 5 matches · 1 protected · 2 exploited · 1 CISA KEV · 3 EPSS ≥ 0.5
Protected by Waratek
2
40.0%
Rule in development
0
0.0%
Mitigation candidate
3
60.0%
No exploit published
0
0.0%
blocked by ARMR today
1
20.0%
partly blocked
1
20.0%
not blocked
3
60.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
40.0%
Working exploit published
1
20.0%
Proof of concept only
2
40.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 1 / year
20101
Protected by Waratek1
Medium1
blocked by ARMR today1
Working exploit published1
20110
20120
20130
20140
20150
20161
Protected by Waratek1
Critical1
partly blocked1
Exploited1
20170
20180
20190
20201
Mitigation candidate1
High1
not blocked1
Proof of concept only1
20211
Mitigation candidate1
Critical1
not blocked1
Exploited1
20221
Mitigation candidate1
Critical1
not blocked1
Proof of concept only1
2010201220142016201820202022
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-32532 | Critical | 2022-06-29 | Mitigation candidate | Proof of concept only | Apache Shiro before 1.9.1, A RegexRequestMatcher can be misconfigured to be bypassed on some servlet containers. Applications using RegExPatternMatcher with `.` in the regular expression are possibly vulnerable to an authorization bypass. |
| 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-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-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. |