dbcve.org
Cf ReleaseApplication · Cloudfoundry

CVE-2017-4972

HIGH · 7.5 CVSS v3.1 Published 2017-06-13
Fix available
A fix is available. Upgrade to after 256 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 v257; UAA release 2.x versions prior to v2.7.4.14, 3.6.x versions prior to v3.6.8, 3.9.x versions prior to v3.9.10, and other versions prior to v3.15.0; and UAA bosh release (uaa-release) 13.x versions prior to v13.12, 24.x versions prior to v24.7, and other versions prior to v30. An attacker can use a blind SQL injection attack to query the contents of the UAA database.

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

A blind SQL injection vulnerability exists in the User Account and Authentication (UAA) component of Cloud Foundry. The flaw allows remote unauthenticated attackers to execute arbitrary SQL queries against the UAA database by injecting malicious SQL statements through vulnerable input parameters.

MitigationUpgrade UAA release to v2.7.4.14+, v3.6.8+, v3.9.10+, v3.15.0+, or v13.12+/v24.7+/v30+ depending on branch; also upgrade cf-release to v257 or later to obtain the patched UAA version.

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
Cf ReleaseApplication
Affected:<= 256
Cloud Foundry Uaa BoshApplication
Affected:<= 29= 13.1= 13.2= 13.3= 13.4= 13.5= 13.6= 13.7= 13.8= 13.9= 13.10= 13.11
Cloud Foundry UaaApplication
Affected:<= 3.15.0= 2.2.5.4= 2.7.1= 2.7.2= 2.7.3= 2.7.4= 2.7.4.1= 2.7.4.2= 2.7.4.3= 2.7.4.4= 2.7.4.5= 2.7.4.6

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

CVSS:3.1/AV:N/AC:L/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 checks

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

  1. Verify UAA network exposure
    Identify the UAA URL in your Cloud Foundry deployment (typically at /uaa path). Check if it is accessible from untrusted networks or the internet without authentication. Review load balancer, firewall, and router rules.
    Affected if UAA is directly accessible from untrusted networks without authentication
  2. Identify UAA version via BOSH
    Run 'bosh vms' to find the UAA VM, then 'bosh ssh' to access it. Check the version using 'cat /var/vcap/packages/uaa-release/VERSION' or check the release manifest with 'bosh manifest | grep -A5 uaa'.
    Affected if UAA version is <= 3.15.0, or equals 2.2.5.4, or falls within 2.7.1 to 2.7.4.6, or falls within 13.1 to 13.11, or <= 29 (BOSH release)
  3. Identify cf-release version
    Run 'bosh releases' or check the deployment manifest to find the cf-release version number.
    Affected if Cf-release version is <= 256
  4. Check UAA endpoint accessibility
    Examine UAA configuration files (uaa.yml or properties in the BOSH manifest) for 'uaa.url' and verify which endpoints are exposed. Specifically check if the '/login' and '/oauth/authorize' endpoints accept unauthenticated requests.
    Affected if UAA login or authorization endpoints accept unauthenticated requests without additional protection
  5. Review UAA database connectivity
    Verify the UAA is using an external database (PostgreSQL or MySQL). Check uaa.yml database configuration section to confirm database type and connection details.
    Affected if UAA is configured with a database that could be targeted by SQL injection

Your environment is affected if UAA is exposed to untrusted network access and the installed UAA version or cf-release version falls within the affected ranges listed above.

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 a release after 256
Interim mitigation

Upgrade UAA release to v2.7.4.14+, v3.6.8+, v3.9.10+, v3.15.0+, or v13.12+/v24.7+/v30+ depending on branch; also upgrade cf-release to v257 or later to obtain the patched UAA version.

Fix this in Cf Release Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-4972 — 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-2017-4972 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