CVE-2016-0715
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 · uneditedPivotal Cloud Foundry Elastic Runtime version 1.4.0 through 1.4.5, 1.5.0 through 1.5.11 and 1.6.0 through 1.6.11 is vulnerable to a remote information disclosure. It was found that original mitigation configuration instructions provided as part of CVE-2016-0708 were incomplete and could leave PHP Buildpack, Staticfile Buildpack and potentially other custom Buildpack applications vulnerable to remote information disclosure. Affected applications use automated buildpack detection, serve files directly from the root of the application and have a buildpack that matched after the Java Buildpack in the system buildpack priority when Java Buildpack versions 2.0 through 3.4 were present.
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 confidencePivotal Cloud Foundry Elastic Runtime versions 1.4.x through 1.6.x contains an incomplete fix from CVE-2016-0708. When PHP Buildpack, Staticfile Buildpack, or custom Buildpacks are used with automated detection and serve files from the root, and the Java Buildpack (versions 2.0-3.4) is present at a higher priority, the applications become vulnerable to remote information disclosure due to improper buildpack handling order.
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>= 1.4.0, <= 1.4.5>= 1.5.0, <= 1.5.11>= 1.6.0, <= 1.6.11CVSS 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.
-
Check Elastic Runtime versionAccess the Cloud Foundry API or Ops Manager interface and retrieve the installed Elastic Runtime versionAffected if Version is between 1.4.0-1.4.5, 1.5.0-1.5.11, or 1.6.0-1.6.11
-
Identify active application buildpacksUse 'cf buildpacks' CLI command or check the manifest.yml for each application to identify which buildpacks are configured for automated detectionAffected if PHP Buildpack, Staticfile Buildpack, or custom Buildpacks are configured with auto-detection on the application
-
Check if Java Buildpack is presentUse 'cf buildpacks' CLI command to list all available buildpacks and identify if Java Buildpack is installedAffected if Java Buildpack versions 2.0 through 3.4 are present in the Cloud Foundry environment
-
Verify buildpack priority orderingUse 'cf buildpacks' CLI command to check the position/priority ranking of buildpacks. Lower position numbers indicate higher priority during detectionAffected if Java Buildpack has a higher priority (lower position number) than PHP Buildpack, Staticfile Buildpack, or custom Buildpacks being used by applications
-
Confirm application serves files from rootReview application configuration and staticfile or index.php settings to determine if the application serves content from the root URL pathAffected if Applications using PHP/Staticfile/custom buildpacks are configured to serve files from the root path
Environment is affected if running Elastic Runtime 1.4.x-1.6.x AND using PHP/Staticfile/custom buildpacks that serve from root AND Java Buildpack 2.0-3.4 is present at a higher priority than the affected buildpacks.
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 Java Buildpack to version 3.5 or later, or reconfigure buildpack priority ordering to ensure affected buildpacks are checked before Java Buildpack, or upgrade Elastic Runtime to a patched version.
- Consultation4.0 h
- Implementation3.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0715 — 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-2016-0715 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