Skip to content

Spring Security vulnerable to Authorization Bypass

High severity GitHub Reviewed Published Dec 20, 2018 to the GitHub Advisory Database • Updated Mar 14, 2024

Package

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

Affected versions

>= 5.1.0, < 5.1.2

Patched versions

5.1.2
maven org.springframework.security:spring-security-oauth2-jose (Maven)
>= 5.1.0, < 5.1.2
5.1.2

Description

Spring Security versions 5.1.x prior to 5.1.2 contain an authorization bypass vulnerability during JWT issuer validation. In order to be impacted, the same private key for an honest issuer and a malicious user must be used when signing JWTs. In that case, a malicious user could fashion signed JWTs with the malicious issuer URL that may be granted for the honest issuer.

References

Published by the National Vulnerability Database Dec 19, 2018
Published to the GitHub Advisory Database Dec 20, 2018
Reviewed Jun 16, 2020
Last updated Mar 14, 2024

Severity

High

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
High
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.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.141%
(50th percentile)

Weaknesses

CVE ID

CVE-2018-15801

GHSA ID

GHSA-27xw-p8v6-9jjr

Source code

Credits

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