Vulnerabilities > Vmware > Spring Framework > 3.0.5
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2014-04-17 | CVE-2014-0054 | Cross-Site Request Forgery (CSRF) vulnerability in multiple products The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External Entity (XXE) issue. | 6.8 |
2014-01-23 | CVE-2013-7315 | Permissions, Privileges, and Access Controls vulnerability in multiple products The Spring MVC in Spring Framework before 3.2.4 and 4.0.0.M1 through 4.0.0.M2 does not disable external entity resolution for the StAX XMLInputFactory, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML with JAXB, aka an XML External Entity (XXE) issue, and a different vulnerability than CVE-2013-4152. | 6.8 |
2014-01-23 | CVE-2013-4152 | Permissions, Privileges, and Access Controls vulnerability in multiple products The Spring OXM wrapper in Spring Framework before 3.2.4 and 4.0.0.M1, when using the JAXB marshaller, does not disable entity resolution, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via an XML external entity declaration in conjunction with an entity reference in a (1) DOMSource, (2) StAXSource, (3) SAXSource, or (4) StreamSource, aka an XML External Entity (XXE) issue. | 6.8 |
2011-10-04 | CVE-2011-2894 | Deserialization of Untrusted Data vulnerability in VMWare Spring Framework and Spring Security 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. | 6.8 |