Shiro vulnerabilitiesAnd the versions its exploited flaws hit.
Shiro is made by Apache. We track 17 published vulnerabilities in it, across 39 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 3 November 2021. If you run Shiro, check your version against the exploited flaws below and patch those first.
The most recent Shiro flaw added to the known-exploited list is CVE-2016-4437, on 3 November 2021. We keep watching the known-exploited list.
Which versions of Shiro do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "before 1.2.5" means every version up to, but not including, 1.2.5. Find your version, then patch.
- CVE-2016-4437Exploited list, 3 Nov 2021
Apache Shiro Code Execution Vulnerability
before 1.2.5
Which Shiro vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8Apache Shiro Code Execution Vulnerability
Apache Shiro contains a vulnerability which may allow remote attackers to execute code or bypass intended access restrictions via an unspecified request parameter when a cipher key has not been configured for the...
Which Shiro flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 93%
Apache Shiro before 1.2.5, when a cipher key has not been configured for the "remember me" feature, allows remote attackers to execute arbitrary code or bypass intended access restrictions via an unspecified request...
- 86%CVE-2020-17523Critical
Apache Shiro before 1.7.1, when using Apache Shiro with Spring, a specially crafted HTTP request may cause an authentication bypass.
- 76%CVE-2021-41303Critical
Apache Shiro before 1.8.0, when using Apache Shiro with Spring Boot, a specially crafted HTTP request may cause an authentication bypass.
- 55%CVE-2010-3863Medium
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...
- 44%CVE-2020-13933High
Apache Shiro before 1.6.0, when using Apache Shiro, a specially crafted HTTP request may cause an authentication bypass.
- 26%CVE-2022-32532Critical
Apache Shiro before 1.9.1, A RegexRequestMatcher can be misconfigured to be bypassed on some servlet containers.
- 24%CVE-2020-11989Critical
Apache Shiro before 1.5.3, when using Apache Shiro with Spring dynamic controllers, a specially crafted request may cause an authentication bypass.
- 23%CVE-2020-1957Critical
Apache Shiro before 1.5.2, when using Apache Shiro with Spring dynamic controllers, a specially crafted request may cause an authentication bypass.
- 9.7%CVE-2016-6802High
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.
- 9.1%CVE-2019-12422High
Apache Shiro before 1.4.2, when using the default "remember me" configuration, cookies could be susceptible to a padding attack.
Running Shiro? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Apache Shiro contains a vulnerability which may allow remote attackers to execute code or bypass intended access restrictions via an unspecified request parameter when a cipher key has not been configured for the "remember me" feature.
- Matched to
- Shiro on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 17 published vulnerabilities listed under the name Shiro, across 39 versions. The most recent Shiro flaw added to the known-exploited list is CVE-2016-4437, on 3 November 2021.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2016-4437.
Each flaw names its own versions, usually as ranges. The newest, CVE-2016-4437, affects before 1.2.5. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Shiro. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.