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.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Link | Tags |
---|---|
http://rhn.redhat.com/errata/RHSA-2016-2035.html | vendor advisory |
http://www.securitytracker.com/id/1036587 | vdb entry |
http://pivotal.io/security/cve-2015-3192 | vendor advisory |
http://rhn.redhat.com/errata/RHSA-2016-2036.html | vendor advisory |
https://access.redhat.com/errata/RHSA-2016:1218 | vendor advisory |
http://www.securityfocus.com/bid/90853 | vdb entry |
http://rhn.redhat.com/errata/RHSA-2016-1592.html | vendor advisory |
http://lists.fedoraproject.org/pipermail/package-announce/2015-July/162015.html | vendor advisory |
http://lists.fedoraproject.org/pipermail/package-announce/2015-July/162017.html | vendor advisory |
https://jira.spring.io/browse/SPR-13136 | |
http://rhn.redhat.com/errata/RHSA-2016-1593.html | vendor advisory |
https://access.redhat.com/errata/RHSA-2016:1219 | vendor advisory |
https://lists.debian.org/debian-lts-announce/2019/07/msg00012.html | mailing list |