CVE-2016-0708
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 · uneditedApplications deployed to Cloud Foundry, versions v166 through v227, may be vulnerable to a remote disclosure of information, including, but not limited to environment variables and bound service details. For applications to be vulnerable, they must have been staged using automatic buildpack detection, passed through the Java Buildpack detection script, and allow the serving of static content from within the deployed artifact. The default Apache Tomcat configuration in the affected java buildpack versions for some basic web application archive (WAR) packaged applications are vulnerable to this issue.
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 confidenceCloud Foundry versions v166-v227 contain a vulnerable default Apache Tomcat configuration in the Java buildpack that allows served static content from within WAR artifacts to expose sensitive environment variables and bound service credentials (including database passwords, API keys, etc.). The vulnerability requires automatic buildpack detection and static content serving enabled.
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>= 166, <= 227>= 2.0, <= 3.4CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 Cloud Foundry release versionRun 'cf --version' or query the Cloud Foundry API at /v2/info to retrieve the 'cc_build_revision' or 'version' field that indicates the CF release numberAffected if The CF release version is greater than or equal to 166 and less than or equal to 227
-
Identify Java Buildpack versionCheck the deployed Java buildpack version by examining the buildpack files in the CF environment or running 'cf buildpacks' to list available buildpacks and their versionsAffected if The Java Buildpack version is greater than or equal to 2.0 and less than or equal to 3.4
-
Confirm automatic buildpack detection is enabledVerify that the application is deployed using automatic buildpack detection (the default behavior) rather than explicitly specifying a buildpack with 'cf push -b'Affected if The application uses automatic buildpack detection, which is the default when no -b flag is specified
-
Check for static content served from WAR artifactsInspect deployed WAR files in the application container or examine the Tomcat server.xml configuration within the Java buildpack to confirm that serving static content from within WAR files is enabled (the default configuration)Affected if Static content serving from within deployed WAR files is enabled in the Tomcat configuration
You are affected if your Cloud Foundry deployment is between versions 166-227, uses Java Buildpack versions 2.0-3.4, relies on automatic buildpack detection, and has default Tomcat configuration that serves static content from WAR files.
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 Cloud Foundry deployment to a version beyond v227, or reconfigure the Java buildpack's Tomcat configuration to prevent serving of sensitive static content from within deployed WAR files.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0708 — 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-0708 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