Apache Shiro Path Traversal vulnerability
Apache Shiro before 1.1.0, and JSecurity 0.9.x, does not canonicalize URI paths before comparing them to entries in the shiro.ini file, which allows remote attackers to bypass intended access restrictions via a crafted request, as demonstrated by the /./account/index.jsp URI.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.apache.shiro:shiro-root | < 1.1.0 | 1.1.0 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2010-3863
- https://exchange.xforce.ibmcloud.com/vulnerabilities/62959
- https://github.com/apache/shiro
- https://web.archive.org/web/20101120091718/http://www.vupen.com/english/advisories/2010/2888
- https://web.archive.org/web/20101129043410/http://secunia.com/advisories/41989
- https://web.archive.org/web/20110929165859/http://www.securityfocus.com/bid/44616
- https://web.archive.org/web/20161017000748/http://www.securityfocus.com/archive/1/514616/100/0/threaded
- http://archives.neohapsis.com/archives/fulldisclosure/2010-11/0020.html
- Weakness (CWE)
CWE-22- Platform
- Java / Kotlin (Maven)
- Package
org.apache.shiro:shiro-root- Disclosed
- 14.05.2022
- Updated
- 11.10.2026 12:21
Sources and licenses
OSV / GitHub Advisory Database - GHSA-3jx9-mgwx-4q83 - CC BY 4.0
Vulnerability history: org.apache.shiro:shiro-root
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 2
- First → latest
- 05.2022 01.2023
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 1
- Medium 1
Disclosures per year
- 2022: 1
- 2023: 1
- 2024: 0
- 2025: 0
- 2026: 0
-
Apache Shiro Path Traversal vulnerability this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.