Skip to content

Spring Security logout not clearing security context

Moderate severity GitHub Reviewed Published Apr 19, 2023 to the GitHub Advisory Database • Updated Nov 8, 2023

Package

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

Affected versions

>= 5.7.0, < 5.7.8
>= 5.8.0, < 5.8.3
>= 6.0.0, < 6.0.3

Patched versions

5.7.8
5.8.3
6.0.3

Description

In Spring Security, versions 5.7.x prior to 5.7.8, versions 5.8.x prior to 5.8.3, and versions 6.0.x prior to 6.0.3, the logout support does not properly clean the security context if using serialized versions. Additionally, it is not possible to explicitly save an empty security context to the HttpSessionSecurityContextRepository. This vulnerability can keep users authenticated even after they performed logout. Users of affected versions should apply the following mitigation. 5.7.x users should upgrade to 5.7.8. 5.8.x users should upgrade to 5.8.3. 6.0.x users should upgrade to 6.0.3.

References

Published by the National Vulnerability Database Apr 19, 2023
Published to the GitHub Advisory Database Apr 19, 2023
Reviewed May 5, 2023
Last updated Nov 8, 2023

Severity

Moderate

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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:L/UI:N/S:U/C:L/I:L/A:L

EPSS score

0.067%
(30th percentile)

Weaknesses

CVE ID

CVE-2023-20862

GHSA ID

GHSA-x873-6rgc-94jc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.