First published: Thu May 25 2017(Updated: )
The Loggregator Traffic Controller endpoints in cf-release v231 and lower, Pivotal Elastic Runtime versions prior to 1.5.19 AND 1.6.x versions prior to 1.6.20 are not cleansing request URL paths when they are invalid and are returning them in the 404 response. This could allow malicious scripts to be written directly into the 404 response.
Credit: security_alert@emc.com
Affected Software | Affected Version | How to fix |
---|---|---|
Cloud Foundry CF Release | <=231 | |
Pivotal Cloud Foundry Elastic Runtime | <=1.5.18 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.0 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.1 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.2 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.3 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.4 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.5 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.6 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.7 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.8 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.9 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.10 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.11 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.12 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.13 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.14 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.15 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.16 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.17 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.18 | |
Pivotal Cloud Foundry Elastic Runtime | =1.6.19 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2016-2165 is categorized as high due to the potential unauthorized access to sensitive data.
To fix CVE-2016-2165, upgrade to Pivotal Elastic Runtime version 1.5.19 or higher, or to 1.6.20 or higher.
CVE-2016-2165 affects Cloud Foundry CF Release versions up to 231 and Pivotal Elastic Runtime versions prior to 1.5.19 and 1.6.x prior to 1.6.20.
CVE-2016-2165 exploits the failure to cleanse invalid request URL paths in the Loggregator Traffic Controller.
CVE-2016-2165 was published in 2016 as part of a security disclosure.