CVE-2016-9878: Path Traversal
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.
Other sources
It was found that paths provided to the ResourceServlet were not properly sanitized and as a result exposed to directory traversal attacks.
Upstream bug:
https://jira.spring.io/browse/SPR-14946
Upstream patches:
https://github.com/spring-projects/spring-framework/commit/e2d6e709c3c65a4951eb096843ee75d5200cfcad https://github.com/spring-projects/spring-framework/commit/43bf008fbcd0d7945e2fcd5e30039bc4d74c7a98 https://github.com/spring-projects/spring-framework/commit/a7dc48534ea501525f11369d369178a60c2f47d0
External References:
https://pivotal.io/security/cve-2016-9878
— Red Hat
Pivotal Spring Framework could allow a remote attacker to traverse directories on the system, caused by the failure to sanitize paths provided to ResourceServlet. An attacker could send a specially-crafted URL request containing directory traversal sequences to view arbitrary files on the system.
— IBM
Affected Software
Event History
Frequently Asked Questions
What is the vulnerability ID for this issue in Pivotal Spring Framework?
The vulnerability ID for this issue in Pivotal Spring Framework is CVE-2016-9878.
What is the severity of CVE-2016-9878?
The severity of CVE-2016-9878 is high with a CVSS score of 7.5.
How does CVE-2016-9878 impact Pivotal Spring Framework?
CVE-2016-9878 allows a remote attacker to traverse directories on the system and view arbitrary files.
Which versions of Pivotal Spring Framework are affected by CVE-2016-9878?
Versions 3.2.0 to 3.2.18, 4.2.0 to 4.2.9, and 4.3.0 to 4.3.5 of Pivotal Spring Framework are affected by CVE-2016-9878.
How can I fix CVE-2016-9878 in Pivotal Spring Framework?
To fix CVE-2016-9878, update Pivotal Spring Framework to version 3.2.18, 4.2.9, or 4.3.5.