CVE-2017-4970: Medium severity cloudfoundry Cf-release vulnerability
An issue was discovered in Cloud Foundry Foundation cf-release v255 and Staticfile buildpack versions v1.4.0 - v1.4.3. A regression introduced in the Static file build pack causes the Staticfile.auth configuration to be ignored when the Static file file is not present in the application root. Applications containing a Staticfile.auth file but not a Static file had their basic auth turned off when an operator upgraded the Static file build pack in the foundation to one of the vulnerable versions. Note that Static file applications without a Static file are technically misconfigured, and will not successfully detect unless the Static file build pack is explicitly specified.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-4970?
CVE-2017-4970 has a medium severity rating due to its potential impact on authentication configuration.
How do I fix CVE-2017-4970?
To fix CVE-2017-4970, you should upgrade to a version of the Cloud Foundry Staticfile buildpack that is not affected, above v1.4.3.
What software does CVE-2017-4970 affect?
CVE-2017-4970 affects Cloud Foundry Foundation cf-release v255 and Staticfile buildpack versions v1.4.0 to v1.4.3.
What is the main issue described in CVE-2017-4970?
The main issue in CVE-2017-4970 is that the Staticfile.auth configuration is ignored when the Staticfile is not present in the application root.
Is CVE-2017-4970 a remotely exploitable vulnerability?
CVE-2017-4970 is not classified as a remotely exploitable vulnerability, but it can impact the security configuration of applications.