ID CVE-2016-0708
Summary Applications deployed to Cloud Foundry, versions v166 through v227, 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.
References
Vulnerable Configurations
  • Cloud Foundry cf-release 166
    cpe:2.3:a:cloudfoundry:cf-release:166
  • Cloud Foundry cf-release 167
    cpe:2.3:a:cloudfoundry:cf-release:167
  • Cloud Foundry cf-release 168
    cpe:2.3:a:cloudfoundry:cf-release:168
  • Cloud Foundry cf-release 169
    cpe:2.3:a:cloudfoundry:cf-release:169
  • Cloud Foundry cf-release 170
    cpe:2.3:a:cloudfoundry:cf-release:170
  • Cloud Foundry cf-release 171
    cpe:2.3:a:cloudfoundry:cf-release:171
  • Cloud Foundry cf-release 172
    cpe:2.3:a:cloudfoundry:cf-release:172
  • Cloud Foundry cf-release 173
    cpe:2.3:a:cloudfoundry:cf-release:173
  • Cloud Foundry cf-release 174
    cpe:2.3:a:cloudfoundry:cf-release:174
  • Cloud Foundry cf-release 175
    cpe:2.3:a:cloudfoundry:cf-release:175
  • Cloud Foundry cf-release 176
    cpe:2.3:a:cloudfoundry:cf-release:176
  • Cloud Foundry cf-release 177
    cpe:2.3:a:cloudfoundry:cf-release:177
  • Cloud Foundry cf-release 178
    cpe:2.3:a:cloudfoundry:cf-release:178
  • Cloud Foundry cf-release 179
    cpe:2.3:a:cloudfoundry:cf-release:179
  • Cloud Foundry cf-release 180
    cpe:2.3:a:cloudfoundry:cf-release:180
  • Cloud Foundry cf-release 181
    cpe:2.3:a:cloudfoundry:cf-release:181
  • Cloud Foundry cf-release 182
    cpe:2.3:a:cloudfoundry:cf-release:182
  • Cloud Foundry cf-release 183
    cpe:2.3:a:cloudfoundry:cf-release:183
  • Cloud Foundry cf-release 184
    cpe:2.3:a:cloudfoundry:cf-release:184
  • Cloud Foundry cf-release 185
    cpe:2.3:a:cloudfoundry:cf-release:185
  • Cloud Foundry cf-release 186
    cpe:2.3:a:cloudfoundry:cf-release:186
  • Cloud Foundry cf-release 187
    cpe:2.3:a:cloudfoundry:cf-release:187
  • Cloud Foundry cf-release 188
    cpe:2.3:a:cloudfoundry:cf-release:188
  • Cloud Foundry cf-release 189
    cpe:2.3:a:cloudfoundry:cf-release:189
  • Cloud Foundry cf-release 190
    cpe:2.3:a:cloudfoundry:cf-release:190
  • Cloud Foundry cf-release 191
    cpe:2.3:a:cloudfoundry:cf-release:191
  • Cloud Foundry cf-release 192
    cpe:2.3:a:cloudfoundry:cf-release:192
  • Cloud Foundry cf-release 193
    cpe:2.3:a:cloudfoundry:cf-release:193
  • Cloud Foundry cf-release 194
    cpe:2.3:a:cloudfoundry:cf-release:194
  • Cloud Foundry cf-release 195
    cpe:2.3:a:cloudfoundry:cf-release:195
  • Cloud Foundry cf-release 196
    cpe:2.3:a:cloudfoundry:cf-release:196
  • Cloud Foundry cf-release 197
    cpe:2.3:a:cloudfoundry:cf-release:197
  • Cloud Foundry cf-release 198
    cpe:2.3:a:cloudfoundry:cf-release:198
  • Cloud Foundry cf-release 199
    cpe:2.3:a:cloudfoundry:cf-release:199
  • Cloud Foundry cf-release 200
    cpe:2.3:a:cloudfoundry:cf-release:200
  • Cloud Foundry cf-release 201
    cpe:2.3:a:cloudfoundry:cf-release:201
  • Cloud Foundry cf-release 202
    cpe:2.3:a:cloudfoundry:cf-release:202
  • Cloud Foundry cf-release 203
    cpe:2.3:a:cloudfoundry:cf-release:203
  • Cloud Foundry cf-release 204
    cpe:2.3:a:cloudfoundry:cf-release:204
  • Cloud Foundry cf-release 205
    cpe:2.3:a:cloudfoundry:cf-release:205
  • Cloud Foundry cf-release 206
    cpe:2.3:a:cloudfoundry:cf-release:206
  • Cloud Foundry cf-release 207
    cpe:2.3:a:cloudfoundry:cf-release:207
  • Cloud Foundry cf-release 208
    cpe:2.3:a:cloudfoundry:cf-release:208
  • Cloud Foundry cf-release 209
    cpe:2.3:a:cloudfoundry:cf-release:209
  • Cloud Foundry cf-release 210
    cpe:2.3:a:cloudfoundry:cf-release:210
  • Cloud Foundry cf-release 211
    cpe:2.3:a:cloudfoundry:cf-release:211
  • Cloud Foundry cf-release 212
    cpe:2.3:a:cloudfoundry:cf-release:212
  • Cloud Foundry cf-release 213
    cpe:2.3:a:cloudfoundry:cf-release:213
  • Cloud Foundry cf-release 214
    cpe:2.3:a:cloudfoundry:cf-release:214
  • Cloud Foundry cf-release 215
    cpe:2.3:a:cloudfoundry:cf-release:215
  • Cloud Foundry cf-release 216
    cpe:2.3:a:cloudfoundry:cf-release:216
  • Cloud Foundry cf-release 217
    cpe:2.3:a:cloudfoundry:cf-release:217
  • Cloud Foundry cf-release 218
    cpe:2.3:a:cloudfoundry:cf-release:218
  • Cloud Foundry cf-release 219
    cpe:2.3:a:cloudfoundry:cf-release:219
  • Cloud Foundry cf-release 220
    cpe:2.3:a:cloudfoundry:cf-release:220
  • Cloud Foundry cf-release 221
    cpe:2.3:a:cloudfoundry:cf-release:221
  • Cloud Foundry cf-release 222
    cpe:2.3:a:cloudfoundry:cf-release:222
  • Cloud Foundry cf-release 223
    cpe:2.3:a:cloudfoundry:cf-release:223
  • Cloud Foundry cf-release 224
    cpe:2.3:a:cloudfoundry:cf-release:224
  • Cloud Foundry cf-release 225
    cpe:2.3:a:cloudfoundry:cf-release:225
  • Cloud Foundry cf-release 226
    cpe:2.3:a:cloudfoundry:cf-release:226
  • Cloud Foundry cf-release 227
    cpe:2.3:a:cloudfoundry:cf-release:227
CVSS
Base: 4.3
Impact:
Exploitability:
CWE CWE-200
CAPEC
  • Subverting Environment Variable Values
    The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
  • Footprinting
    An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Browser Fingerprinting
    An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
refmap via4
confirm https://www.cloudfoundry.org/blog/cve-2016-0708/
Last major update 11-07-2018 - 16:29
Published 11-07-2018 - 16:29
Last modified 11-09-2018 - 14:49
Back to Top