Threat Intelligence Database

"Remember me" cookie age is not verified on the server. This potentially allows an attacker to intercept a valid cookie and reuse it indefinitely, even after the configured expiration time has passed. This issue affects all Apache Shiro versions from 1.2.4 through 2.x, and 3.0.0-alpha-1, only when RememberMe functionality is enabled. Upgrade to version 3.0.0 or later, which fixes the issue.

Apache Shiro versions 1.0 through 2.1.0 and 3.0.0-alpha-1 have a vulnerability where sensitive cookies (JSESSIONID and rememberMe) used in HTTPS sessions are sent without the 'Secure' attribute by default. This omission can expose these cookies to interception over non-secure channels. The issue is fixed in versions 2.1.1 and 3.0.0-alpha-2 or later.

Authentication Bypass by Alternate Name vulnerability in Apache Shiro. This issue affects Apache Shiro: before 2.0.7. Users are recommended to upgrade to version 2.0.7, which fixes the issue. The issue only effects static files. If static files are served from a case-insensitive filesystem, such as default macOS setup, static files may be accessed by varying the case of the filename in the request. If only lower-case (common default) filters are present in Shiro, they may be bypassed this way. Shiro 2.1.0 and later has a new parameters to remediate this issue shiro.ini: filterChainResolver.caseInsensitive = true application.properties: shiro.caseInsensitive=true Shiro 3.0.0 and later makes this the default in shiro.ini-based configurations. Shiro 3.0.1 and later makes this the default in all configurations, including programmatic and Spring / Spring Boot.

MediumVulnerabilityGermanyFranceNetherlands+5#cve#cve-2026-23903#cwe-289