Authorization annotations, such as @RequiresRoles and @RequiresPermissions, are not always...
影響パッケージ
| パッケージ | 影響を受ける版 → 修正版 | |
|---|---|---|
| Apache Software FoundationApache Shiro |
2.0.0-alpha-0 以上 3.0.2 未満→ 3.0.2 |
3.0.2 |
ディストリビューション別の修正状況
各ディストリビューションが公開している、この CVE の記録です。修正版は配布版ごとに違うので、リンク先で確かめてください。
- Debian DEBIAN-CVE-2026-74763 shiro この記録に修正版の記載なし
- Ubuntu UBUNTU-CVE-2026-74763 shiro この記録に修正版の記載なし
原文の説明 取得元が公開している説明をそのまま載せています (多くは英語)。
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.
出典: oss-security (Openwall) NVD GitHub Advisory