# Improper Access Control in Apache Shiro

Advisory record · `GHSA-4q2v-j639-cp7p`

- **Identifiers:** `GHSA-4q2v-j639-cp7p` · `CVE-2016-6802`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 14 May 2022
- **Updated:** 8 Nov 2023
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2022, 02:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.shiro:shiro-all` (Maven): affected `<1.3.2`; fixed in `1.3.2`
- `org.apache.shiro:shiro-web` (Maven): affected `<1.3.2`; fixed in `1.3.2`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.097, the 95th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 14 May 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-4q2v-j639-cp7p](https://github.com/advisories/GHSA-4q2v-j639-cp7p)
- [OSV: GHSA-4q2v-j639-cp7p](https://osv.dev/vulnerability/GHSA-4q2v-j639-cp7p)
- <https://nvd.nist.gov/vuln/detail/CVE-2016-6802>
- <https://github.com/apache/shiro/commit/b15ab927709ca18ea4a02538be01919a19ab65af>
- <https://issues.apache.org/jira/browse/SHIRO-584>
- <https://packetstormsecurity.com/files/138709/Apache-Shiro-Filter-Bypass.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4q2v-j639-cp7p>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4q2v-j639-cp7p/>. Everything for agents: <https://agentprime.io/llms.txt>.
