Skip to content

GHSA-v33x-prhc-gph5 CVE-2019-11272

Insufficiently Protected Credentials and Improper Authentication in Spring Security

High Maven
Severity
7.3 / 10
High · CVSS 3.1
Exploit chance (EPSS)
1.38%
Chance of exploitation in the next 30 days. Higher than 72.16% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-287 Improper Authentication
CWE-522 Insufficiently Protected Credentials
Fix
Available
2 packages have a fixed version

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?.

Affected versions

Maven

PackageVulnerableFixed in
org.springframework.security:spring-security-cas
< 4.2.13.RELEASE
4.2.13.RELEASE
org.springframework.security:spring-security-core
< 4.2.13
4.2.13

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.springframework.security:spring-security-cas Maven → 4.2.13.RELEASE

maven
<dependency><groupId>org.springframework.security</groupId><artifactId>spring-security-cas</artifactId><version>4.2.13.RELEASE</version></dependency>
gradle
implementation("org.springframework.security:spring-security-cas:4.2.13.RELEASE")

org.springframework.security:spring-security-core Maven → 4.2.13

maven
<dependency><groupId>org.springframework.security</groupId><artifactId>spring-security-core</artifactId><version>4.2.13</version></dependency>
gradle
implementation("org.springframework.security:spring-security-core:4.2.13")

Severity breakdown

CVSS 3.1 7.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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

Weakness

CWE-287: Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

How to prevent it
  • Architecture and Design: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.

CWE-522: Insufficiently Protected Credentials

The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

How to prevent it
  • Architecture and Design: Use an appropriate security mechanism to protect the credentials.
  • Architecture and Design: Make appropriate use of cryptography to protect the credentials.
  • Implementation: Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-vxf7-qj7q-83fh
Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider
Low Also affects org.springframework.security:spring-security-core
GHSA-x2wq-9x2f-fhj7
Spring Security Core has a TOCTOU race condition when One-Time Token login with JdbcOneTimeTokenService is configured
Medium Also affects org.springframework.security:spring-security-core
GHSA-vqxh-445g-37fc
Spring Security has a broken timing attack mitigation implemented in DaoAuthenticationProvide
Medium Also affects org.springframework.security:spring-security-core
GHSA-8v5q-rhf3-jphm
Spring Security annotation detection mechanism has authorization bypass
High Also affects org.springframework.security:spring-security-core
GHSA-9pp5-9c7g-4r83
Spring Security authorization bypass for method security annotations on private methods
Critical Also affects org.springframework.security:spring-security-core
GHSA-hh3m-g4qj-4835
Spring Security Vulnerable to Authorization Bypass via Security Annotations
Medium Also affects org.springframework.security:spring-security-core
GHSA-q3v6-hm2v-pw99
Spring Framework has Authorization Bypass for Case Sensitive Comparisons
Medium Also affects org.springframework.security:spring-security-core
GHSA-hmqf-wpq9-jq83
Spring Security Missing Authorization vulnerability
High Also affects org.springframework.security:spring-security-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor