First published: Tue Oct 04 2011(Updated: )
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.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.springframework.security:spring-security-core | >=2.0.0<2.0.7 | 2.0.7 |
maven/org.springframework.security:spring-security-core | >=3.0.0<3.0.6 | 3.0.6 |
maven/org.springframework:spring-core | >=3.0.0<3.0.6 | 3.0.6 |
Spring Framework | >=3.0.0<=3.0.5 | |
VMware Spring Security | >=2.0.0<=2.0.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-2894 has been rated as a high severity vulnerability due to its potential for remote code execution.
To fix CVE-2011-2894, upgrade Spring Framework to version 3.0.6 or Spring Security to version 2.0.7 or higher.
CVE-2011-2894 affects Spring Framework versions 3.0.0 through 3.0.5 and Spring Security versions 2.0.0 through 2.0.6.
Yes, CVE-2011-2894 can be exploited remotely by attackers to execute untrusted code.
CVE-2011-2894 allows attackers to bypass security restrictions and execute arbitrary code through deserialization of untrusted data.