Apache Shiro: Authorization annotations not always enforced, depending on where they are placed
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 3.0.2.
Authorization annotations, such as @RequiresRoles and @RequiresPermissions, are not always enforced in some class or interface hierarchies. Annotations declared on an interface were not enforced when using the shiro-guice, shiro-aspectj, shiro-cdi or shiro-jakarta-ee modules. In addition, annotations declared on a class or a superclass were not always enforced when using shiro-guice or shiro-aspectj, allowing an unauthorized caller to invoke methods that should be protected. This issue affects all Apache Shiro versions through 3.0.1, with impact depending on module and where annotations are declared. Mitigation: Upgrade to version 3.0.2 or later, which fixes the issue. The annotation closest to the invoked method now takes precedence. Alternatively, declare authorization annotations directly on each protected implementing method.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Apache Software Foundation | <3.0.2, >=2.0.0-alpha-0 <3.0.2 | 3.0.2 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket