Apache Shiro: Authorization annotations not always enforced, depending on where they are placed
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache Shiro | unaffected |
|
||||||
| Apache Software Foundation | Apache Shiro | unaffected |
|
||||||
| Apache Software Foundation | Apache Shiro | unaffected |
|
||||||
| Apache Software Foundation | Apache Shiro | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Apache Shiro: Authorization annotations not always enforced, depending on where they are placed | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV4_0
|
No data.
Missing Authorization
No data.
No data.
No data.
No data.