cve.bz

CVE-2019-11272 Insufficiently Protected Credentials

7.3 highEPSS 1.4%Fix available

High (7.3). EPSS 1.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.security:spring-security-core 4.2.13.

On this page
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".

Severity

CVSS 3.1

7.3 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
1.4% (unchanged from 1.4% a week ago; 1.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 74th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-522 Insufficiently Protected Credentials
CWE-287 Improper Authentication
OWASP Top 10
A06:2025 Insecure Design, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-11272 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-11272?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-11272?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-11272 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring Securityfrom 4.2 before 4.2.13.RELEASE

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v33x-prhc-gph5Mavenorg.springframework.security:spring-security-core<4.2.134.2.13
GHSA-v33x-prhc-gph5Mavenorg.springframework.security:spring-security-cas<4.2.13.RELEASE4.2.13.RELEASE

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian8libspring-security-2.0-java2.0.7.RELEASE-3+deb8u2DLA-1848-1

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat OpenStack Platform's OpenDaylight versions 9 and 10 contain the vulnerable code. However, these OpenDaylight versions were released as technical preview with limited support and will therefore not be updated. Other OpenDaylight versions do not contain the vulnerable library.

ProductPackageStateAdvisory
Red Hat Fuse 7.6.0spring-security-coreFixed 2020-03-26RHSA-2020:0983
Red Hat JBoss Fuse 6spring-security-coreOut of support scope
Red Hat OpenStack Platform 10 (Newton)opendaylightNot affected
Red Hat OpenStack Platform 13 (Queens)opendaylightNot affected
Red Hat OpenStack Platform 14 (Rocky)opendaylightNot affected
Red Hat OpenStack Platform 8 (Liberty)opendaylightWill not fix
Red Hat OpenStack Platform 9 (Mitaka)opendaylightWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2019-11272.

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-522 (13).

References

Check your stackJSON