Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2017-4970

5.9 · MEDIUM
Published Jun 13, 2017 cloudfoundry EPSS 0.69% (50th pctl)

Overview

CVE-2017-4970 is a medium-severity vulnerability affecting cloudfoundry cf-release. It was published on June 13, 2017 and has a CVSS 3.0 base score of 5.9 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 5.9, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories and patches from cloudfoundry. Update cf-release to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status

Frequently Asked Questions

What is CVE-2017-4970?

CVE-2017-4970 is a medium-severity vulnerability affecting cloudfoundry cf-release. It was published on June 13, 2017 and has a CVSS 3.0 base score of 5.9 (MEDIUM).

How severe is CVE-2017-4970?

This vulnerability has a CVSS 3.0 base score of 5.9, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2017-4970?

Check the references section for vendor advisories and patches from cloudfoundry. Update cf-release to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2017-4970?

CyberStrike's AI-powered security agents can automatically detect CVE-2017-4970 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.