shiro-core CVEs · Protected by Waratek

Protected by Waratek 2 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%

Critical 1 50.0% High 0 0.0% Medium 1 50.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%

blocked by ARMR today 1 50.0% partly blocked 1 50.0% not blocked 0 0.0% not established 0 0.0% unrecorded 0 0.0%

Exploited 1 50.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 1 50.0%

split by StatusSeverityProtectionExploit maturity peak 1 / year

20161 Protected by Waratek1 Critical1 partly blocked1 Exploited1 20170 20180 20190 20200 20210 20220 20230 20241 Protected by Waratek1 Medium1 blocked by ARMR today1 No public exploit1

201620172018201920202021202220232024

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-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

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-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.