Patchfirst
CVE-2010-3863 Public exploit EPSS 54.5%

Apache Shiro before 1.1.0, and JSecurity 0.9.x, does not canonicalize URI paths before comparing them to entries in…

Fix:upgrade shiro-root to 1.1.0 or later Details ↓

Summary

Apache Shiro before 1.1.0 and JSecurity 0.9.x fail to canonicalize URI paths before matching them against entries in the shiro.ini file, so access-control rules are evaluated against the raw request path. A remote, unauthenticated attacker can send a crafted request, such as one using a path variant like /./account/index.jsp, to bypass intended access restrictions.

Official description · CVE.org

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 crafted request, as demonstrated by the /./account/index.jsp URI.

Breakdown
26.2 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15

Public exploit code (Exploit-DB) was available 3 days before disclosure.

  1. Public exploit codeExploit-DB3 days before
  2. Disclosedday 0

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: org.apache.shiro:shiro-root.

Mavenorg.apache.shiro:shiro-rootGHSA-3jx9-mgwx-4q83

Upgrade to 1.1.0 or later

Set the version to 1.1.0 or later in your pom.xml or build.gradle.

The first fix for CVE-2010-3863. No other CVE tracked by Patchfirst affects this package.

Affected versions

If you runUpgrade to
All versions before 1.1.01.1.0

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

Also mentioned in 3 community threat pulses (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

References

7 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close