Skip to content

Spring Security authorization rules can be bypassed via forward or include dispatcher types

Critical severity GitHub Reviewed Published Nov 1, 2022 to the GitHub Advisory Database • Updated Jan 31, 2023

Package

maven org.springframework.security:spring-security-core (Maven)

Affected versions

>= 5.7.0, < 5.7.5
>= 5.6.0, < 5.6.9

Patched versions

5.7.5
5.6.9

Description

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)

References

Published by the National Vulnerability Database Oct 31, 2022
Published to the GitHub Advisory Database Nov 1, 2022
Reviewed Nov 1, 2022
Last updated Jan 31, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.129%
(49th percentile)

Weaknesses

CVE ID

CVE-2022-31692

GHSA ID

GHSA-mmmh-wcxm-2wr4
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.