# CVE-2010-3863: Apache Shiro Path Traversal vulnerability

> Remote attackers can bypass access restrictions in Apache Shiro by using crafted URI paths that are not canonicalized before comparison.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Nov 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3jx9-mgwx-4q83

## What is CVE-2010-3863?

CVE-2010-3863 is a medium-severity authentication bypass vulnerability in n/a, published on 5 Nov 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2010-3863?

2 open source packages ship an affected version, including org.apache.shiro:shiro-root. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.shiro:shiro-root` | Maven | All versions | 1.1.0 |
| `org.apache.shiro:shiro-root` | Maven | All versions | 1.1.0 |

Products: Apache Shiro, Jsecurity Jsecurity.

## How do I fix CVE-2010-3863?

Upgrade org.apache.shiro:shiro-root to 1.1.0 or later.

## Is CVE-2010-3863 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-3863 exists.

Public exploit code:

- shiro 路径穿越 (github_poc): https://github.com/sh1inroot-alt/shiro-cve-2010-3863
- Apache Shiro - Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2023-34478](https://insights.sbomify.com/CVE-2023-34478/): Path Traversal in Apache Shiro (critical 9.8)
- [CVE-2022-40664](https://insights.sbomify.com/CVE-2022-40664/): Authentication Bypass Vulnerability in Shiro when forwarding or including via RequestDispatcher (critical 9.8)
- [CVE-2022-32532](https://insights.sbomify.com/CVE-2022-32532/): Authentication Bypass Vulnerability (critical 9.8)
- [CVE-2021-41303](https://insights.sbomify.com/CVE-2021-41303/): Apache Shiro vulnerable to a specially crafted HTTP request causing an authentication bypass (critical 9.8)
- [CVE-2020-17523](https://insights.sbomify.com/CVE-2020-17523/): Authentication bypass in Apache Shiro (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3863 and fix it if it is affected.

What it is: CVE-2010-3863 is a medium-severity authentication bypass vulnerability in n/a, published on 5 Nov 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-3863 exists.

Affected packages and fixed versions:
- org.apache.shiro:shiro-root (Maven): affected all versions; fixed in 1.1.0
- org.apache.shiro:shiro-root (Maven): affected all versions; fixed in 1.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2010-3863/ (Markdown: https://insights.sbomify.com/CVE-2010-3863/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-3863
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-3863
- OSV: https://osv.dev/vulnerability/CVE-2010-3863

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-3863/
Summaries are generated and may contain mistakes; the official description above is the record.