CWE
22
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2023-46749: Apache Shiro before 1.13.0 or 2.0.0-alpha-4, may be susceptible to a path traversal attack that results in an authentication bypass when used together with path rewriting

First published: Fri Jan 12 2024(Updated: )

Apache Shiro before 1.13.0 or 2.0.0-alpha-4, may be susceptible to a path traversal attack that results in an authentication bypass when used together with path rewriting Mitigation: Update to Apache Shiro 1.13.0+ or 2.0.0-alpha-4+, or ensure `blockSemicolon` is enabled (this is the default).

Credit: security@apache.org security@apache.org

Affected SoftwareAffected VersionHow to fix
Apache Shiro<1.13.0
Apache Shiro=2.0.0-alpha1
Apache Shiro=2.0.0-alpha2
Apache Shiro=2.0.0-alpha3
maven/org.apache.shiro:shiro-core>=2.0.0alpha1<2.0.0alpha4
2.0.0-alpha4
maven/org.apache.shiro:shiro-core<1.13.0
1.13.0
IBM Cognos Analytics<=12.0.0-12.0.2
IBM Cognos Analytics<=11.2.0-11.2.4 FP3
redhat/shiro<1.13.0
1.13.0
redhat/shiro 2.0.0-alpha<4
4
debian/shiro
1.3.2-4+deb11u1
1.3.2-5
<1.13.0
=2.0.0-alpha1
=2.0.0-alpha2
=2.0.0-alpha3

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2023-46749?

    CVE-2023-46749 has a high severity due to the potential for authentication bypass through a path traversal attack.

  • How do I fix CVE-2023-46749?

    To fix CVE-2023-46749, update to Apache Shiro version 1.13.0 or higher, or 2.0.0-alpha-4 or higher.

  • Which versions of Apache Shiro are affected by CVE-2023-46749?

    Apache Shiro versions before 1.13.0 and 2.0.0-alpha-4 are affected by CVE-2023-46749.

  • What is a path traversal attack in the context of CVE-2023-46749?

    In the context of CVE-2023-46749, a path traversal attack allows an attacker to bypass authentication by manipulating URL paths.

  • Is enabling blockSemicolon an effective mitigation for CVE-2023-46749?

    Yes, enabling blockSemicolon can be an effective mitigation for CVE-2023-46749 if upgrading is not immediately possible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203