dbcve.org
ShiroApplication · Apache

CVE-2022-40664

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-12
Fix available
A fix is available. Upgrade to 1.10.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Apache Shiro before 1.10.0, Authentication Bypass Vulnerability in Shiro when forwarding or including via RequestDispatcher.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Shiro before 1.10.0 contains an authentication bypass vulnerability where specially crafted requests using RequestDispatcher forward or include operations can circumvent the authentication filter, allowing unauthenticated attackers to access protected resources.

MitigationUpgrade Apache Shiro to version 1.10.0 or later to apply the authentication bypass fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ShiroApplication
Affected:< 1.10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Shiro version
    Locate the shiro-core jar file in the application lib directory, or check the pom.xml/build.gradle for the Shiro dependency version. Common paths: WEB-INF/lib/, or search for 'shiro-core' in dependency files.
    Affected if The installed Shiro version is earlier than 1.10.0 (for example, 1.9.1, 1.9.0, 1.8.0, etc.)
  2. Locate Shiro filter configuration
    Find the web.xml file (or equivalent Java configuration) that defines the ShiroFilter. Look for a filter definition with class org.apache.shiro.web.servlet.ShiroFilter or similar.
    Affected if A ShiroFilter is configured and active in the web application.
  3. Examine filter chain URL patterns
    In the Shiro filter configuration, review the filter chain definitions (url patterns mapped to filters like authc, authcBasic, etc.). Identify which paths require authentication.
    Affected if Protected URL patterns exist that require authentication (mapped to authc, authcBasic, or other authentication filters).
  4. Check for vulnerable forward/include access
    Determine whether untrusted users can submit requests that trigger a RequestDispatcher forward or include operation to reach protected resources. This typically involves JSP files or servlets that forward to protected paths, or applications with dynamic path handling.
    Affected if The application contains JSP files or servlets that perform RequestDispatcher forward() or include() operations to protected URL paths accessible by unauthenticated users.

The environment is affected if Apache Shiro version is below 1.10.0 and the application allows unauthenticated users to trigger RequestDispatcher forward or include operations that reach protected resources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.10.0 or later
Fixed in 1.10.0
Interim mitigation

Upgrade Apache Shiro to version 1.10.0 or later to apply the authentication bypass fix.

Recommended fix High confidence

1.10.0

  1. Identify all applications and dependencies using Apache Shiro version < 1.10.0 in your environment
  2. Update the Shiro dependency to version 1.10.0 or later in your build configuration (e.g., Maven pom.xml, Gradle build.gradle, or library management system)
  3. Rebuild the application with the updated dependency
  4. Redeploy the updated application to all affected environments
  5. Verify that authentication functionality continues to work correctly after the update
  6. Confirm the version has been successfully applied by checking the Shiro version at runtime

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Shiro Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-40664 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data