dbcve.org
Spring SecurityFramework / library · VMware

CVE-2022-31692

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-31
Fix available
A fix is available. Upgrade to 5.6.9 / 5.7.5 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
Spring Security, versions 5.7 prior to 5.7.5 and 5.6 prior to 5.6.9 could be susceptible to authorization rules bypass via forward or include dispatcher types. Specifically, an application is vulnerable when all of the following are true: The application expects that Spring Security applies security to forward and include dispatcher types. The application uses the AuthorizationFilter either manually or via the authorizeHttpRequests() method. The application configures the FilterChainProxy to apply to forward and/or include requests (e.g. spring.security.filter.dispatcher-types = request, error, async, forward, include). The application may forward or include the request to a higher privilege-secured endpoint.The application configures Spring Security to apply to every dispatcher type via authorizeHttpRequests().shouldFilterAllDispatcherTypes(true)

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

Spring Security versions 5.7.x prior to 5.7.5 and 5.6.x prior to 5.6.9 contain an authorization bypass vulnerability where the AuthorizationFilter does not properly apply security rules when requests are forwarded or included to higher-privilege endpoints, specifically when shouldFilterAllDispatcherTypes(true) is configured.

MitigationUpgrade to Spring Security 5.7.5+ or 5.6.9+, or explicitly set shouldFilterAllDispatcherTypes(false) and configure dispatcher-types to exclude forward/include unless required for functionality.

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
Spring SecurityFramework / library
Affected:>= 5.6.0, < 5.6.9>= 5.7.0, < 5.7.5
Active Iq Unified ManagerApplication
Affected:all versions

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 Spring Security version
    Locate the Spring Security dependency in your build configuration (pom.xml, build.gradle) or check the compiled library version in the classpath. Common paths: Maven POM shows spring-security-version property, or inspect the spring-security-core-*.jar file.
    Affected if Version is 5.6.0 through 5.6.8, or 5.7.0 through 5.7.4
  2. Verify shouldFilterAllDispatcherTypes configuration
    Search your Spring Security configuration files (Java config classes or XML config) for calls to shouldFilterAllDispatcherTypes(true) or dispatcherTypeDefaults() that include FORWARD or INCLUDE types.
    Affected if shouldFilterAllDispatcherTypes is explicitly set to true, or dispatcherTypeDefaults is configured to include FORWARD and INCLUDE dispatcher types
  3. Confirm forwarded/included request handling exists
    Review your controller mappings and view resolvers to determine if any endpoints use request forwarding (forward: prefix) or resource inclusion (include:). Check for JSP forward directives or ViewControllers that forward to higher-privilege endpoints.
    Affected if Your application forwards requests to or includes resources from endpoints that require higher privileges than the originating request
  4. Check NetApp Active IQ Unified Manager
    If using NetApp Active IQ Unified Manager, note that all versions are affected regardless of Spring Security version configuration.
    Affected if NetApp Active IQ Unified Manager is deployed in your environment

You are affected if you run Spring Security 5.6.0-5.6.8 or 5.7.0-5.7.4 AND have shouldFilterAllDispatcherTypes(true) configured (or equivalent dispatcher type settings) while your application forwards or includes requests to higher-privilege endpoints.

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 5.6.9 / 5.7.5 or later
Fixed in 5.6.95.7.5
Interim mitigation

Upgrade to Spring Security 5.7.5+ or 5.6.9+, or explicitly set shouldFilterAllDispatcherTypes(false) and configure dispatcher-types to exclude forward/include unless required for functionality.

Recommended fix High confidence

Spring Security 5.6.9+ or 5.7.5+ (recommended: latest 5.7.x stable release)

  1. Identify the Spring Security version in your project by checking your build configuration (pom.xml for Maven or build.gradle for Gradle)
  2. Upgrade Spring Security to version 5.6.9 or higher if using the 5.6.x line
  3. Upgrade Spring Security to version 5.7.5 or higher if using the 5.7.x line
  4. Rebuild and redeploy your application
  5. Verify that authorization rules are still correctly enforced after the upgrade
  6. For Active IQ Unified Manager, check NetApp's official security advisory for product-specific patches
Caveat Minor: Review any custom security configurations that may rely on specific dispatcher type behaviors; the fix changes how forward/include requests are handled

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

Fix this in Spring Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31692 — 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-31692 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