Skip to content

Grails Spring Security Core plugin: Improper Privilege Management vulnerability

Critical
mattmoss published GHSA-frqg-vvxg-jqqh Nov 22, 2022

Package

grails-spring-security-core (Grails 5)

Affected versions

< 5.1.1

Patched versions

5.1.1
grails-spring-security-core (Grails 4)
< 4.0.5
4.0.5
grails-spring-security-core (Grails 3)
3.x
3.3.2
grails-spring-security-core (Grails 2)
2.x
N/A
grails-spring-security-core (Grails 1)
1.x
N/A

Description

Impact

The vulnerability allows an attacker access to one endpoint (i.e. the targeted endpoint) using the authorization requirements of a different endpoint (i.e. the donor endpoint). In some Grails framework applications using the Grails Spring Security Core (GSSC) plugin, access to the targeted endpoint will be granted based on meeting the authorization requirements of the donor endpoint, which can result in a privilege escalation attack.

Patches

The vulnerability has been patched in GSSC plugin versions 3.3.2, 4.0.5, and 5.1.1.

Workarounds

If you are unable to upgrade to a patched version of the plugin, the GSSC-CVE-2022-41923 repository contains workarounds for GSSC plugin versions 2.x through 5.x. The workaround is especially important for version 2.x, as no patch is available version 2.x of the GSSC plugin.

References

Please see the Grails blog post for additional information and updates.

For more information

If you have any questions or comments about this advisory:

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
None

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:N

CVE ID

CVE-2022-41923

Weaknesses