Summary
Spring Framework 3.0.0 through 3.0.5, Spring Security 3.0.0 through 3.0.5 and 2.0.0 through 2.0.6, and possibly other versions deserialize objects from untrusted sources, which allows remote attackers to bypass intended security restrictions and execute untrusted code by (1) serializing a java.lang.Proxy instance and using InvocationHandler, or (2) accessing internal AOP interfaces, as demonstrated using deserialization of a DefaultListableBeanFactory instance to execute arbitrary commands via the java.lang.Runtime class.
Impact
Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
org.springframework:spring-core to 3.0.6 or later; org.springframework.security:spring-security-core to 3.0.6 or later; org.springframework.security:spring-security-core to 2.0.7 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2011-2894? CVE-2011-2894 is a medium-severity insecure deserialization vulnerability in org.springframework:spring-core (maven), affecting versions >= 3.0.0, < 3.0.6. It is fixed in 3.0.6, 2.0.7. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
- Which packages are affected by CVE-2011-2894?
org.springframework:spring-core(maven) (versions >= 3.0.0, < 3.0.6)org.springframework.security:spring-security-core(maven) (versions >= 3.0.0, < 3.0.6)
- Is there a fix for CVE-2011-2894? Yes. CVE-2011-2894 is fixed in 3.0.6, 2.0.7. Upgrade to this version or later.
- Is CVE-2011-2894 exploitable, and should I be worried? Whether CVE-2011-2894 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2011-2894 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2011-2894?
- Upgrade
org.springframework:spring-coreto 3.0.6 or later - Upgrade
org.springframework.security:spring-security-coreto 3.0.6 or later - Upgrade
org.springframework.security:spring-security-coreto 2.0.7 or later
- Upgrade