CVE-2011-2894: Spring Framework and Spring Security vulnerable to Deserialization of Untrusted Data

Quick answers

Is CVE-2011-2894 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2011-2894 being exploited in the wild.

How severe is CVE-2011-2894?

Informational severity, published 14 May 2022.

Which products and versions are affected?

org.springframework:spring-core (Maven) ECOSYSTEM:introduced=3.0.0,fixed=3.0.6; org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=3.0.0,fixed=3.0.6.

Is there a fix for CVE-2011-2894?

Yes. org.springframework:spring-core (Maven): upgrade to 3.0.6 or later; org.springframework.security:spring-security-core (Maven): upgrade to 3.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2011-2894?

Check whether you run org.springframework:spring-core (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:spring-core (Maven): upgrade to 3.0.6 or later

  # set org.springframework:spring-core to 3.0.6 in your pom.xml or build.gradle

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

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

Affected products

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

Identifiers

• CVE-2011-2894
• GHSA-f866-m9mv-2xr3