CVE-2017-4969
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 · uneditedThe Cloud Controller in Cloud Foundry cf-release versions prior to v255 allows authenticated developer users to exceed memory and disk quotas for tasks.
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 confidenceIn Cloud Foundry cf-release versions prior to v255, the Cloud Controller component fails to properly enforce memory and disk quota restrictions for tasks. Authenticated developer users can exceed their allocated quotas by manipulating task configurations, potentially leading to resource exhaustion and denial of service.
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<= 254CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cloud Foundry deploymentCheck for the presence of Cloud Controller API (CC) by querying the /v2/info endpoint of the Cloud Controller or reviewing deployment manifests for cf-release componentsAffected if Cloud Foundry cf-release with Cloud Controller component is present
-
Determine cf-release versionRun 'cf curl /v2/info' to retrieve the cc_api_version or check the deployment manifest/releases directory for the exact cf-release version numberAffected if cf-release version is 254 or lower (v255 and later are patched)
-
Verify Cloud Controller task functionalityCheck if the Cloud Controller has task endpoints enabled by running 'cf curl /v2/tasks' - a successful response indicates task functionality is activeAffected if Task endpoints return 200 OK, confirming task creation is available to developers
-
Check for developer role accessReview user roles in Cloud Foundry using 'cf curl /v2/users' and verify if any users have developer permissions on organizations/spaces by querying 'cf curl /v2/organizations/:guid/developers'Affected if Developer users exist who can create and manipulate tasks
A user is affected if running cf-release version 254 or lower AND the Cloud Controller task functionality is enabled for authenticated developer users.
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 cf-release to version v255 or later to obtain the patched Cloud Controller that properly enforces developer task quotas.
- 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-2017-4969 — 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-4969 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