CVE-2016-6802
Shiro: Security servlet filters bypass
Overview
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.
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 3.0 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness: CWE-284
Affected packages · 2
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Maven | org.apache.shiro:shiro-all | <1.3.2 | 1.3.2 |
| Maven | org.apache.shiro:shiro-web | <1.3.2 | 1.3.2 |
Open a package to see all its vulnerabilities.
Operating systems · 5 fixes
debian 4 releases · 1 package
fixed 4
shiro
| Release | Package | Fixed in |
|---|---|---|
| 11 | shiro | 1.3.2-1 |
| 12 | shiro | 1.3.2-1 |
| 13 | shiro | 1.3.2-1 |
| 14 | shiro | 1.3.2-1 |
echo 1 release · 1 package
fixed 1
shiro
| Release | Package | Fixed in |
|---|---|---|
| shiro | 1.3.2-1 |
References
- openwall.com http://openwall.com/lists/oss-security/2016/09/13/3
- packetstormsecurity.com http://packetstormsecurity.com/files/138709/Apache-Shiro-Filter-Bypass.html
- www.securityfocus.com http://www.securityfocus.com/archive/1/539397/100/0/threaded
- www.securityfocus.com http://www.securityfocus.com/bid/92947
- access.redhat.com https://access.redhat.com/security/cve/CVE-2016-6802
- github.com https://github.com/apache/shiro/commit/b15ab927709ca18ea4a02538be01919a19ab65af
- issues.apache.org https://issues.apache.org/jira/browse/SHIRO-584
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2016-6802
- packetstormsecurity.com https://packetstormsecurity.com/files/138709/Apache-Shiro-Filter-Bypass.html
- ubuntu.com https://ubuntu.com/security/notices/USN-7147-1
Show all 11 references
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.