First published: Tue Jan 14 2014(Updated: )
It was found that the Spring MVC SourceHttpMessageConverter processed user-provided XML, and did not expose any property for disabling entity resolution in the XML. A remote attacker could use this flaw to conduct XML External Entity (XXE) attacks on web sites, and read files in the context of the user running the application server. The patch for this flaw disables external entity processing by default, and provides a configuration directive to re-enable it. This flaw is considered to be the result of an incomplete fix for <a href="https://access.redhat.com/security/cve/CVE-2013-4152">CVE-2013-4152</a>.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Security Directory Suite VA | <=8.0.1-8.0.1.19 | |
Pivotal Software Spring Framework | >=3.0.0<=3.2.4 | |
VMware Spring Framework | =4.0.0-milestone1 | |
VMware Spring Framework | =4.0.0-milestone2 | |
VMware Spring Framework | =4.0.0-rc1 | |
maven/org.springframework:spring-web | <=3.2.4.RELEASE | 3.2.5.RELEASE |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2013-6429 is medium with a score of 6.8.
CVE-2013-6429 allows remote attackers to read arbitrary files, cause denial of service, and conduct CSRF attacks via crafted XML.
Spring Framework versions before 3.2.5 and 4.0.0.M1 through 4.0.0.RC1 are affected by CVE-2013-6429.
Yes, updating to Spring Framework version 3.2.5 or newer, or version 4.0.0.RC2 or newer, will fix CVE-2013-6429.
You can find more information about CVE-2013-6429 on the Red Hat Security website, the Spring Framework GitHub repository, and the Pivotal website.