Source: shiro X-Debbugs-CC: [email protected] Severity: grave Tags: security
Hi, The following vulnerabilities were published for shiro. It's not clear to which extend these affect the EOLed 1.x branch in sid: CVE-2026-49268[0]: | A remote attacker can inject LDAP special characters into the | Distinguished Name (DN) construction in DefaultLdapRealm class. | User-supplied username input is directly concatenated into the LDAP | DN template without any escaping of RFC 2253 special characters. | This allows an attacker to manipulate the DN structure used for LDAP | bind authentication, potentially bypassing authentication or | impersonating other users. This issue affects all Apache Shiro | versions through 2.2.0, and 3.0.0-alpha-1 when | using DefaultLdapRealm Upgrade to Apache Shiro 2.2.1 or | 3.0.0-alpha-2 or later, which fixes the issue. CVE-2026-74762[1]: https://www.openwall.com/lists/oss-security/2026/11/14/5 https://shiro.apache.org/security-reports.html#cve_2026_74762 CVE-2026-74763[2]: https://www.openwall.com/lists/oss-security/2026/11/14/4 https://shiro.apache.org/security-reports.html#cve_2026_74763 CVE-2026-88019[3]: https://www.openwall.com/lists/oss-security/2026/11/14/3 https://shiro.apache.org/security-reports.html#cve_2026_88019 CVE-2026-56091[4]: | When using Apache Shiro with the shiro-guice module in a web servlet | context, a specially crafted HTTP request may cause an | authentication bypass. This vulnerability is similar to | https://www.cve.org/CVERecord?id=CVE-2020-1957 | https://www.cve.org/CVERecord , except that it affects the `shiro- | guice` module instead of the `shiro-spring` module. This issue | affects all Apache Shiro versions through 2.x, and 3.0.0-alpha-1 | only when using `shiro-guice` module in a web servlet context. | Upgrade to version 3.0.0 or later, which fixes the issue. https://lists.apache.org/thread/onmtxmy2qonbpx7xlw3o34x8sctv47r7 CVE-2026-56130[5]: | "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. https://www.openwall.com/lists/oss-security/2026/06/24/8 CVE-2026-129320[6]: https://www.openwall.com/lists/oss-security/2026/11/14/2 https://shiro.apache.org/security-reports.html#cve_2026_129320 CVE-2026-129347[7]: https://www.openwall.com/lists/oss-security/2026/11/14/6 https://shiro.apache.org/security-reports.html#cve_2026_129347 CVE-2026-129348[8]: https://www.openwall.com/lists/oss-security/2026/11/14/7 https://shiro.apache.org/security-reports.html#cve_2026_129348 CVE-2026-129349[9]: | When authentication caching is enabled on DefaultLdapRealm, after a | user logs in successfully once, subsequent logins for that user | succeed with any password. A cached authentication skips the LDAP | bind, and the AllowAllCredentialsMatcher installed by default in | DefaultLdapRealm accepts any credentials, allowing an attacker who | knows a valid username to authenticate as that user. This issue | affects all Apache Shiro versions through 3.0.0, only when using | DefaultLdapRealm (or JndiLdapRealm) with | authenticationCachingEnabled set to true, which is not the default. | Mitigation: Upgrade to version 3.0.1 or later, which fixes the issue | by no longer installing AllowAllCredentialsMatcher by default. | Alternatively, disable authentication caching on the LDAP realm | (this is the default), or configure a credentials matcher, such as | SimpleCredentialsMatcher, that verifies credentials against the | cached authentication info. https://www.openwall.com/lists/oss-security/2026/11/14/8 https://shiro.apache.org/security-reports.html#cve_2026_129349 If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2026-49268 https://www.cve.org/CVERecord?id=CVE-2026-49268 [1] https://security-tracker.debian.org/tracker/CVE-2026-74762 https://www.cve.org/CVERecord?id=CVE-2026-74762 [2] https://security-tracker.debian.org/tracker/CVE-2026-74763 https://www.cve.org/CVERecord?id=CVE-2026-74763 [3] https://security-tracker.debian.org/tracker/CVE-2026-88019 https://www.cve.org/CVERecord?id=CVE-2026-88019 [4] https://security-tracker.debian.org/tracker/CVE-2026-56091 https://www.cve.org/CVERecord?id=CVE-2026-56091 [5] https://security-tracker.debian.org/tracker/CVE-2026-56130 https://www.cve.org/CVERecord?id=CVE-2026-56130 [6] https://security-tracker.debian.org/tracker/CVE-2026-129320 https://www.cve.org/CVERecord?id=CVE-2026-129320 [7] https://security-tracker.debian.org/tracker/CVE-2026-129347 https://www.cve.org/CVERecord?id=CVE-2026-129347 [8] https://security-tracker.debian.org/tracker/CVE-2026-129348 https://www.cve.org/CVERecord?id=CVE-2026-129348 [9] https://security-tracker.debian.org/tracker/CVE-2026-129349 https://www.cve.org/CVERecord?id=CVE-2026-129349 Please adjust the affected versions in the BTS as needed.

