CVE-2016-9878

An issue was discovered in Pivotal Spring Framework before 3.2.18, 4.2.x before 4.2.9, and 4.3.x before 4.3.5. Paths provided to the ResourceServlet were not properly sanitized and as a result exposed to directory traversal attacks.

An issue was discovered in Pivotal Spring Framework before 3.2.18, 4.2.x before 4.2.9, and 4.3.x before 4.3.5. Paths provided to the ResourceServlet were not properly sanitized and as a result exposed to directory traversal attacks.

TuxCare rebuilt 6 org.springframework packages to address 25 CVEs. Fixed in 4.0.0.RELEASE-tuxcare.1.

TuxCare rebuilt 7 org.springframework packages to address 29 CVEs. Fixed in 3.1.1.RELEASE-tuxcare.1.

TuxCare rebuilt 3 org.springframework packages to address 3 CVEs. Fixed in 3.0.5.RELEASE-tuxcare.2.

TuxCare rebuilt 3 org.springframework packages to address 3 CVEs. Fixed in 4.3.4.RELEASE-tuxcare.1.

Toshiaki Maki discovered that Spring Framework incorrectly handled certain XML files. A remote attacker could exploit this with a crafted XML file to cause a denial of service. (CVE-2015-3192)

Alvaro Muñoz discovered that Spring Framework incorrectly handled certain URLs. A remote attacker could possibly use this issue to cause a reflected file download. (CVE-2015-5211)

It was discovered that Spring Framework did not properly sanitize path inputs. An attacker could possibly use this issue to read arbitrary files, resulting in a directory traversal attack (CVE-2016-9878)

It was discovered that Spring Framework incorrectly handled XML documents. An attacker could possibly use this issue to generate an XML external entity attack, resulting in a denial of service, disclosure of information or other unspecified impact. This issue only affected Ubuntu 14.04 ESM. (CVE-2014-0225)

It was discovered that Spring Framework incorrectly handled certain URLs. A remote attacker could possibly use this issue to read arbitrary files, resulting in a directory traversal attack. This issue only affected Ubuntu 14.04 ESM. (CVE-2014-3625, CVE-2014-3578)