Overview 4 matches · 3 protected · 2 exploited · 1 CISA KEV · 2 public PoC · 2 EPSS ≥ 0.5
Protected by Waratek
4
100.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
0
0.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
3
75.0%
partly blocked
1
25.0%
not blocked
0
0.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
50.0%
Working exploit published
1
25.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
1
25.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
20200
20210
20220
20231
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
20241
Protected by Waratek1
Medium1
blocked by ARMR today1
No public exploit1
20102012201420162018202020222024
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2023-46749 | Medium | 2024-01-15 | Protected by Waratek | No public exploit | Apache Shiro before 1.13.0 or 2.0.0-alpha-4, may be susceptible to a path traversal attack that results in an authentication bypass when used together with path rewriting Mitigation: Update to Apache Shiro 1.13.0+ or 2.0.0-alpha-4+, or ensure `blockSemicolon` is enabled (this is the default). |
| CVE-2023-34478 | Critical | 2023-07-24 | Protected by Waratek | Exploited | Apache Shiro, before 1.12.0 or 2.0.0-alpha-3, may be susceptible to a path traversal attack that results in an authentication bypass when used together with APIs or other web frameworks that route requests based on non-normalized requests. Mitigation: Update to Apache Shiro 1.12.0+ or 2.0.0-alpha-3+ |
| 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. |