org.apache.shiro:shiro-core vulnerabilities
- Registry
- Maven
- Latest
- 3.0.2
13 known advisories
The latest version, 3.0.2, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.apache.shiro:shiro-core -DdepVersion=3.0.2 -DforceVersion=trueIs your project on an affected org.apache.shiro:shiro-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.apache.shiro:shiro-core
Apache Shiro's "remember me" cookie age is not verified on the server.
- Affected
- >=1.2.4 <3.0.0
- Fixed in
- 3.0.0
Apache Shiro: LDAP DN Injection in DefaultLdapRealm
- Affected
- <2.2.1 · >=3.0.0-alpha-0 <3.0.0-alpha-2
- Fixed in
- 2.2.1, 3.0.0-alpha-2
Apache Shiro has a session fixation vulnerability
- Affected
- >=1.0.0-incubating <2.2.0 · >=3.0.0-alpha-1 <3.0.0-alpha-2
- Fixed in
- 2.2.0, 3.0.0-alpha-2
Apache Shiro Affected by an Observable Timing Discrepancy Vulnerability
- Affected
- <2.1.0
- Fixed in
- 2.1.0
Apache Shiro vulnerable to path traversal
- Affected
- <1.13.0 · >=2.0.0alpha1 <2.0.0-alpha4
- Fixed in
- 1.13.0, 2.0.0-alpha4
Apache Shiro Authentication Bypass vulnerability
- Affected
- <1.10.0
- Fixed in
- 1.10.0
Improper Authorization in Apache Shiro
- Affected
- <1.9.1
- Fixed in
- 1.9.1
Improper Access Control in Apache Shiro
- Affected
- <1.2.5
- Fixed in
- 1.2.5
Apache Shiro vulnerable to a specially crafted HTTP request causing an authentication bypass
- Affected
- <1.8.0
- Fixed in
- 1.8.0
Authentication bypass in Apache Shiro
- Affected
- <1.6.0
- Fixed in
- 1.6.0
Improper Authentication in Apache Shiro
- Affected
- <1.5.2
- Fixed in
- 1.5.2
Improper Authentication in Apache Shiro
- Affected
- <1.5.3
- Fixed in
- 1.5.3
Improper input validation in Apache Shiro
- Affected
- <1.4.2
- Fixed in
- 1.4.2
Is your org.apache.shiro:shiro-core version vulnerable?
- org.apache.shiro:shiro-core 3.0No known advisories in 3.0.2
- org.apache.shiro:shiro-core 2.21 advisory in 2.2.1
- org.apache.shiro:shiro-core 2.13 advisories in 2.1.0
- org.apache.shiro:shiro-core 2.04 advisories in 2.0.6
- org.apache.shiro:shiro-core 1.134 advisories in 1.13.0
- org.apache.shiro:shiro-core 1.125 advisories in 1.12.0
- org.apache.shiro:shiro-core 1.115 advisories in 1.11.0
- org.apache.shiro:shiro-core 1.105 advisories in 1.10.1
- org.apache.shiro:shiro-core 1.96 advisories in 1.9.1
- org.apache.shiro:shiro-core 1.87 advisories in 1.8.0
Which of your client projects still run an old org.apache.shiro:shiro-core?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.