Cloud Foundry Foundation
- Cloud Foundry v166 through v227
- Cloud Foundry Java Buildpack v2.0 through v3.4
Applications deployed to Cloud Foundry may be vulnerable to a remote disclosure of information, including, but not limited to environment variables and bound service details. For applications to be vulnerable, they must have been staged using automatic buildpack detection, passed through the Java Buildpack detection script, and allow the serving of static content from within the deployed artifact. The default Apache Tomcat configuration in the affected java buildpack versions for some basic web application archive (WAR) packaged applications are vulnerable to this issue.
Cloud Foundry users are strongly encouraged to follow one of the mitigations below:
- Upgrade to Cloud Foundry v228 or later using a configuration option that remediates the issue. Details of the required configuration option are available on the cf-release v228 github release page  and the diego-release v0.1446.0 github release page 
- Upgrade the Java Buildpack to v3.5.1  or later and restage all applications that use automated buildpack detection
If only the Java Buildpack mitigation is used, it is required that all applications using automated buildpack detection are re-staged to remediate this issue.
It is possible that sensitive application information may have been disclosed before the remediation, therefore it is recommended that applications using automated buildpack detection rotate credentials including environment variables for bound services, user-provided service instances, and developer provided environment variables. Most Service Brokers provide new credentials to each application using an unbind-service and bind-service sequence of commands.
-  https://github.com/cloudfoundry/cf-release/releases/tag/v228
-  https://github.com/cloudfoundry-incubator/diego-release/releases/tag/v0.1446.0
-  https://github.com/cloudfoundry/java-buildpack/releases/tag/v3.5.1
2015-Jan-18: Initial vulnerability report published.