CVE-2017-4970

UnknownEPSS 0.69%

Last modified

CVE-2017-4970 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.69% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
0.69%

48.1th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
CloudfoundryCf-Release255
CloudfoundryStaticfile Buildpack1.4.0
CloudfoundryStaticfile Buildpack1.4.1
CloudfoundryStaticfile Buildpack1.4.2
CloudfoundryStaticfile Buildpack1.4.3

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-4970?
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.
How severe is CVE-2017-4970?
Severity scoring for CVE-2017-4970 is pending analysis. The EPSS model estimates a 0.69% probability of exploitation in the next 30 days.
How do I fix CVE-2017-4970?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-4970?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST