Cloud Foundry Staticfile Buildpack 1.4.3
Approved changes feed: RSS · Atom
cpe:2.3:a:cloudfoundry:staticfile_buildpack:1.4.3:*:*:*:*:*:*:*
part: a version: 1.4.3 update: *
| Vendor | Cloudfoundry (3aa6768c-437d-5100-a420-b037598cadb4) |
|---|---|
| Product | Staticfile Buildpack (319dc884-1abf-52d2-a581-b41c05016d75) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/cloudfoundry/staticfile-buildpack |
purl2cpe | 2026-06-01 10:12:04.761104 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2017-4970 |
vulnerable | 2026-06-03 14:37:18.160058 |
Details available
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.
Published: 2017-06-13T06:00:00.000Z
Updated: 2024-08-05T14:47:43.684Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.