dbcve.org
Capi ReleaseApplication · Cloudfoundry

CVE-2016-8219

MEDIUM · 6.5 CVSS v3.1 Published 2017-06-13
Fix available
A fix is available. Upgrade to 1.12.0 / 250 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An issue was discovered in Cloud Foundry Foundation cf-release versions prior to 250 and CAPI-release versions prior to 1.12.0. A user with the SpaceAuditor role is over-privileged with the ability to restage applications. This could cause application downtime if the restage fails.

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 confidence

In Cloud Foundry cf-release versions prior to 250 and CAPI-release versions prior to 1.12.0, the SpaceAuditor role is over-privileged with the ability to restage applications, a capability that should be restricted to higher-privileged roles. This unauthorized restaging capability could cause application downtime if the restage operation fails.

MitigationUpgrade cf-release to version 250 or later and CAPI-release to version 1.12.0 or later to remove the unauthorized restage permission from the SpaceAuditor role.

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
Capi ReleaseApplication
Affected:< 1.12.0
Cf ReleaseApplication
Affected:< 250

CVSS 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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check cf-release version
    Determine the installed version of cf-release in your Cloud Foundry deployment and compare it to version 250
    Affected if Installed version is prior to 250
  2. Check CAPI-release version
    Determine the installed version of CAPI-release in your Cloud Foundry deployment and compare it to version 1.12.0
    Affected if Installed version is prior to 1.12.0
  3. Identify active SpaceAuditor roles
    Query your Cloud Foundry deployment for users assigned the SpaceAuditor role in any organization or space
    Affected if Any SpaceAuditor users exist and either cf-release is before 250 or CAPI-release is before 1.12.0

Your environment is affected if you are running cf-release before version 250 or CAPI-release before version 1.12.0, and you have users assigned the SpaceAuditor role who could potentially misuse the unauthorized restage capability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.12.0 / 250 or later
Fixed in 1.12.0250
Interim mitigation

Upgrade cf-release to version 250 or later and CAPI-release to version 1.12.0 or later to remove the unauthorized restage permission from the SpaceAuditor role.

Fix this in Capi Release Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-8219 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-8219 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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