# CVE-2019-11272: Insufficiently Protected Credentials and Improper Authentication in Spring Security

Source: https://junglewise.ai/threats/cve-2019-11272-insufficiently-protected-credentials-and-improper-authentication  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2019-06-27  
License: CC BY 4.0 with a link back

CVE-2019-11272 · Severity: low · CVSS 3.1 · Published 2019-06-27

Insufficiently Protected Credentials and Improper Authentication in Spring Security

Technologies: [org.springframework.security:spring-security-core (Maven)](https://junglewise.ai/threats/technologies/org-springframework-security-spring-security-core). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2019-11272 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2019-11272 being exploited in the wild.

**How severe is CVE-2019-11272?** Low severity, with a CVSS score of 3.1, published 27 June 2019.

**Which products and versions are affected?** org.springframework.security:spring-security-cas (Maven) ECOSYSTEM:introduced=0,fixed=4.2.13.RELEASE; org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=0,fixed=4.2.13.

**Is there a fix for CVE-2019-11272?** Yes. org.springframework.security:spring-security-cas (Maven): upgrade to 4.2.13.RELEASE or later; org.springframework.security:spring-security-core (Maven): upgrade to 4.2.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2019-11272?** Check whether you run org.springframework.security:spring-security-cas (Maven) or org.springframework.security:spring-security-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.springframework.security:spring-security-cas (Maven): upgrade to 4.2.13.RELEASE or later

  ```sh
  # set org.springframework.security:spring-security-cas to 4.2.13.RELEASE in your pom.xml or build.gradle
  ```

- org.springframework.security:spring-security-core (Maven): upgrade to 4.2.13 or later

  ```sh
  # set org.springframework.security:spring-security-core to 4.2.13 in your pom.xml or build.gradle
  ```


## Affected products

- org.springframework.security:spring-security-cas (Maven) ECOSYSTEM:introduced=0,fixed=4.2.13.RELEASE
- org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=0,fixed=4.2.13

## Identifiers

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

## Related threats

- [Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider](https://junglewise.ai/threats/cve-2026-22746-spring-security-vulnerable-to-user-attribute-enumeration-when)
- [Spring Spring Security TOCTOU race condition in JdbcOneTimeTokenService](https://junglewise.ai/threats/cve-2026-22751-spring-spring-security-toctou-race-condition-in)
- [Spring Security has a broken timing attack mitigation implemented in DaoAuthenticationProvide](https://junglewise.ai/threats/cve-2025-22234-spring-security-has-a-broken-timing-attack-mitigation-implemented)
- [Spring Security annotation detection mechanism has authorization bypass](https://junglewise.ai/threats/cve-2025-41248-spring-security-annotation-detection-mechanism-has-authorization)
- [Spring Security authorization bypass for method security annotations on private methods](https://junglewise.ai/threats/cve-2025-41232-spring-security-authorization-bypass-for-method-security)