How severe is CVE-2012-5055?

No CVSS score has been assigned to CVE-2012-5055 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-5055?

CVE-2012-5055 affects the following packages: org.springframework.security:spring-security-core (Maven), org.springframework.security:spring-security-core (Maven), org.springframework.security:spring-security-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-5055?

Update org.springframework.security:spring-security-core to 2.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-5055 is resolved across your whole dependency graph.

How do I detect CVE-2012-5055 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-5055 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2012-5055 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-5055 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-5055?

CVE-2012-5055 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 80th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2012-5055?

CVE-2012-5055 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-5055 published, and has it been updated?

CVE-2012-5055 was published on May 17, 2022 and was last updated on December 7, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2012-5055 — spring-security-core

CVE-2012-5055 is a Information Exposure vulnerability in org.springframework.security:spring-security-core. A fix is available for org.springframework.security:spring-security-core — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in Spring Security

Published

May 17, 2022

Updated

Dec 7, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

DaoAuthenticationProvider in VMware SpringSource Spring Security before 2.0.8, 3.0.x before 3.0.8, and 3.1.x before 3.1.3 does not check the password if the user is not found, which makes the response delay shorter and might allow remote attackers to enumerate valid usernames via a series of login requests.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.security:spring-security-core`	all versions	2.0.8`org.springframework.security:spring-security-core:2.0.8`
☕Maven	`org.springframework.security:spring-security-core`	≥ 3.0.0&&< 3.0.8	3.0.8`org.springframework.security:spring-security-core:3.0.8`
☕Maven	`org.springframework.security:spring-security-core`	≥ 3.1.0&&< 3.1.3	3.1.3`org.springframework.security:spring-security-core:3.1.3`

Affected Products

1 product · 15 configurations

Application

springsource spring securityvmware

≤ 2.0.6

14 versions

2.0.02.0.12.0.22.0.32.0.42.0.53.0.03.0.13.0.23.0.33.0.43.0.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.security:spring-security-core to 2.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-5055 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

RHSA-2013:0649Fuse ESB Enterprise 7.1.0

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-5055 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works