# CVE-2016-6802: Improper Access Control in Apache Shiro

> Attackers can bypass servlet filters and gain unauthorized access when Apache Shiro is deployed in a non-root servlet context path.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 20 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-6802, GHSA-4q2v-j639-cp7p, UBUNTU-CVE-2016-6802

## What is CVE-2016-6802?

CVE-2016-6802 is a high-severity authentication bypass vulnerability in n/a, published on 20 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Shiro before 1.3.2 allows attackers to bypass intended servlet filters and gain access by leveraging use of a non-root servlet context path.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-6802?

4 open source packages ship an affected version, including org.apache.shiro:shiro-all and org.apache.shiro:shiro-web. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.shiro:shiro-all` | Maven | All versions | 1.3.2 |
| `org.apache.shiro:shiro-all` | Maven | All versions | 1.3.2 |
| `org.apache.shiro:shiro-web` | Maven | All versions | 1.3.2 |
| `org.apache.shiro:shiro-web` | Maven | All versions | 1.3.2 |

Products: Apache Shiro.

## How do I fix CVE-2016-6802?

Upgrade org.apache.shiro:shiro-all to 1.3.2 or later.

## Is CVE-2016-6802 being exploited?

There is no known exploitation of CVE-2016-6802 in the wild and no public exploit code.

## 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-2016-6802 and fix it if it is affected.

What it is: CVE-2016-6802 is a high-severity authentication bypass vulnerability in n/a, published on 20 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6802 in the wild and no public exploit code.

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

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-2016-6802/ (Markdown: https://insights.sbomify.com/CVE-2016-6802/index.md)
```

## Sources

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

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