First published: Fri Jul 03 2015(Updated: )
Pivotal Spring Framework before 3.2.14 and 4.x before 4.1.7 do not properly process inline DTD declarations when DTD is not entirely disabled, which allows remote attackers to cause a denial of service (memory consumption and out-of-memory errors) via a crafted XML file.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Pivotal Software Spring Framework | =3.2.0 | |
VMware Spring Framework | =3.2.1 | |
VMware Spring Framework | =3.2.2 | |
VMware Spring Framework | =3.2.3 | |
VMware Spring Framework | =3.2.4 | |
VMware Spring Framework | =3.2.5 | |
VMware Spring Framework | =3.2.6 | |
VMware Spring Framework | =3.2.7 | |
VMware Spring Framework | =3.2.8 | |
VMware Spring Framework | =3.2.9 | |
VMware Spring Framework | =3.2.10 | |
VMware Spring Framework | =3.2.11 | |
VMware Spring Framework | =3.2.12 | |
VMware Spring Framework | =3.2.13 | |
Fedoraproject Fedora | =21 | |
Fedoraproject Fedora | =22 | |
Pivotal Software Spring Framework | =4.1.0 | |
VMware Spring Framework | =4.1.1 | |
VMware Spring Framework | =4.1.2 | |
VMware Spring Framework | =4.1.3 | |
VMware Spring Framework | =4.1.4 | |
VMware Spring Framework | =4.1.5 | |
VMware Spring Framework | =4.1.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.