CVE-2017-4970
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA regression in Cloud Foundry's Staticfile buildpack versions v1.4.0 through v1.4.3 causes the Staticfile.auth configuration to be ignored when the Staticfile itself is not present in the application root. This means applications relying on basic authentication via Staticfile.auth (but lacking a Staticfile) unexpectedly have authentication disabled after upgrading to these vulnerable buildpack versions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 255= 1.4.0= 1.4.1= 1.4.2= 1.4.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Staticfile buildpack versionRun 'cf buildpacks' or inspect your Cloud Foundry deployment manifest to list installed buildpacks and their versions. Look for the Staticfile buildpack entry.Affected if The buildpack version is 1.4.0, 1.4.1, 1.4.2, or 1.4.3
-
Locate application root directoryAccess the deployed application filesystem via 'cf files <appname>' or by examining the application source code repository. Identify the application root where buildpack detection occurs.Affected if The application root is accessible for inspection
-
Check for Staticfile.auth presenceLook for a file named 'Staticfile.auth' in the application root directory. This file configures basic authentication for Staticfile apps.Affected if Staticfile.auth file exists in the application root
-
Check for Staticfile presenceLook for a file named 'Staticfile' (without .auth) in the application root directory. This is the main configuration file for Staticfile buildpack.Affected if Staticfile (without .auth) is ABSENT from the application root while Staticfile.auth is present
Your environment is affected if the Staticfile buildpack version is 1.4.0 through 1.4.3 AND your application has a Staticfile.auth file but lacks a Staticfile file, causing basic authentication to be unexpectedly disabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the Staticfile buildpack to a version beyond v1.4.3 and audit applications using Staticfile.auth to ensure they also contain a proper Staticfile to restore intended authentication behavior.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-4970 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-4970 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data