dbcve.org
Cf ReleaseApplication · Cloudfoundry

CVE-2017-4974

MEDIUM · 6.5 CVSS v3.1 Published 2017-06-13
Fix available
A fix is available. Upgrade to after 30 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 v258; UAA release 2.x versions prior to v2.7.4.15, 3.6.x versions prior to v3.6.9, 3.9.x versions prior to v3.9.11, and other versions prior to v3.16.0; and UAA bosh release (uaa-release) 13.x versions prior to v13.13, 24.x versions prior to v24.8, and other versions prior to v30.1. An authorized user can use a blind SQL injection attack to query the contents of the UAA database, aka "Blind SQL Injection with privileged UAA endpoints."

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

Blind SQL injection vulnerability in Cloud Foundry UAA (User Account and Authentication) allows authenticated users to query the UAA database via SQL injection in privileged endpoints. The vulnerability exists in multiple UAA versions across cf-release, UAA release, and UAA bosh release.

MitigationUpgrade UAA to the fixed versions (v2.7.4.15+, v3.6.9+, v3.9.11+, v3.16.0+, v13.13+, v24.8+, v30.1+) or apply relevant security patches to prevent unauthorized database queries.

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:<= v257
Cloud Foundry Uaa BoshApplication
Affected:<= 30= 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:<= 4.2.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify UAA version via API
    Make a GET request to the /uaa/info endpoint of your Cloud Foundry UAA (e.g., https://uaa.your-domain.uaa/info) and extract the 'version' field from the JSON response
    Affected if The returned version falls within the affected ranges: <= 4.2.0, = 2.7.x series (2.7.1 through 2.7.4.6), = 2.2.5.4, or <= v257 for cf-release
  2. Check UAA version from BOSH manifest
    Locate the BOSH deployment manifest for your UAA release (typically in your deployment repository or via 'bosh manifest' command) and find the 'version' or 'release' section for the UAA job
    Affected if The UAA release version is <= 30, or matches any of: 13.1, 13.2, 13.3, 13.4, 13.5, 13.6, 13.7, 13.8, 13.9, 13.10, or 13.11
  3. Verify UAA patch level
    Query the UAA /uaa/info endpoint and look for a 'patchVersion' or 'build' field if available; otherwise consult your UAA release notes or deployed WAR/JAR file metadata
    Affected if The patch version is below 2.7.4.15 (for 2.7.x), below 3.6.9, below 3.9.11, below 3.16.0, below 13.13, below 24.8, or below 30.1
  4. Confirm privileged endpoint exposure
    Check if your UAA exposes the admin or privileged API endpoints (typically under /uaa/*) to authenticated users by reviewing your UAA routing configuration and API access policies
    Affected if Authenticated users with elevated privileges can access UAA admin endpoints, which is the condition required to exploit the SQL injection

Your environment is affected if the installed UAA version falls within any of the affected version ranges listed and authenticated users have access to privileged UAA endpoints.

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 30
Interim mitigation

Upgrade UAA to the fixed versions (v2.7.4.15+, v3.6.9+, v3.9.11+, v3.16.0+, v13.13+, v24.8+, v30.1+) or apply relevant security patches to prevent unauthorized database queries.

Fix this in Cf Release Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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