CVE-2012-5055: Exposure of Sensitive Information to an Unauthorized Actor in Spring Security

CVE-2012-5055 · Severity: info · Published 2022-05-17

Exposure of Sensitive Information to an Unauthorized Actor in Spring Security

Technologies: org.springframework.security:spring-security-core (Maven). Vendors: Maven.

Quick answers

Is CVE-2012-5055 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2012-5055 being exploited in the wild.
How severe is CVE-2012-5055?
Informational severity, published 17 May 2022.
Which products and versions are affected?
org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=0,fixed=2.0.8.
Is there a fix for CVE-2012-5055?
Yes. org.springframework.security:spring-security-core (Maven): upgrade to 2.0.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2012-5055?
Check whether you run 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-core (Maven): upgrade to 2.0.8 or later
    # set org.springframework.security:spring-security-core to 2.0.8 in your pom.xml or build.gradle

Affected products

  • org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=0,fixed=2.0.8

Identifiers

  • CVE-2012-5055
  • GHSA-3533-rvpc-6x56

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.