Skip to content

Insufficiently Protected Credentials and Improper Authentication in Spring Security

High severity GitHub Reviewed Published Jun 27, 2019 to the GitHub Advisory Database • Updated Jan 28, 2023

Package

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

Affected versions

<= 4.2.12.RELEASE

Patched versions

4.2.13.RELEASE
maven org.springframework.security:spring-security-core (Maven)
<= 4.2.12
4.2.13

Description

Spring Security, versions 4.2.x up to 4.2.12, and older unsupported versions support plain text passwords using PlaintextPasswordEncoder. If an application using an affected version of Spring Security is leveraging PlaintextPasswordEncoder and a user has a null encoded password, a malicious user (or attacker) can authenticate using a password of ?null?.

References

Published by the National Vulnerability Database Jun 26, 2019
Reviewed Jun 27, 2019
Published to the GitHub Advisory Database Jun 27, 2019
Last updated Jan 28, 2023

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

EPSS score

0.083%
(37th percentile)

Weaknesses

CVE ID

CVE-2019-11272

GHSA ID

GHSA-v33x-prhc-gph5

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.