CVE-2017-4974: 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…
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.97% (FIRST EPSS); higher than 62.6% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: org.cloudfoundry.identity:cloudfoundry-identity-server (Maven) 2.7.4.15, 3.6.9, 3.16.0.
Low priority for now. Upgrade to org.cloudfoundry.identity:cloudfoundry-identity-server (Maven) 2.7.4.15, 3.6.9, 3.16.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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."
- Published
- Jun 13, 2017
- Updated
- Jun 16, 2026
- EPSS
- 0.9% · 62th percentile
- CWE
- CWE-89
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| cloudfoundry | cf-release | cpe:2.3:a:cloudfoundry:cf-release |
| cloudfoundry | cloud foundry uaa bosh | cpe:2.3:a:cloudfoundry:cloud_foundry_uaa_bosh |
| pivotal software | cloud foundry uaa | cpe:2.3:a:pivotal_software:cloud_foundry_uaa |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (dell). Independent of NVD's CPE analysis and usually ahead of it.
n/a Cloud Foundry UAA
- Cloud Foundry UAAaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- cloudfoundry cf-releaseup to v257 inclusive
- cloudfoundry cloud foundry uaa boshup to 30 inclusive
- cloudfoundry cloud foundry uaa bosh13.1
- cloudfoundry cloud foundry uaa bosh13.10
- cloudfoundry cloud foundry uaa bosh13.11
- cloudfoundry cloud foundry uaa bosh13.12
- cloudfoundry cloud foundry uaa bosh13.2
- cloudfoundry cloud foundry uaa bosh13.3
- cloudfoundry cloud foundry uaa bosh13.4
- cloudfoundry cloud foundry uaa bosh13.5
- cloudfoundry cloud foundry uaa bosh13.6
- cloudfoundry cloud foundry uaa bosh13.7
- cloudfoundry cloud foundry uaa bosh13.8
- cloudfoundry cloud foundry uaa bosh13.9
- cloudfoundry cloud foundry uaa bosh24
- cloudfoundry cloud foundry uaa bosh24.1
- cloudfoundry cloud foundry uaa bosh24.2
- cloudfoundry cloud foundry uaa bosh24.3
- cloudfoundry cloud foundry uaa bosh24.4
- cloudfoundry cloud foundry uaa bosh24.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.cloudfoundry.identity:cloudfoundry-identity-server | from 2.0.0 · before 2.7.4.15 | 2.7.4.15 |
| Maven | org.cloudfoundry.identity:cloudfoundry-identity-server | from 3.0.0 · before 3.6.9 | 3.6.9 |
| Maven | org.cloudfoundry.identity:cloudfoundry-identity-server | from 3.10.0 · before 3.16.0 | 3.16.0 |
| Maven | org.cloudfoundry.identity:cloudfoundry-identity-server | from 3.7.0 · before 3.9.11 | 3.9.11 |
Same product
cloudfoundry: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-5172Cloud Foundry Runtime cf-release before 216, UAA before 2.5.2, and Pivotal Cloud Foundry (PCF) Elastic Runtime before 1.7.0 allow attackers…39Monitor
- CVE-2015-5171The password change functionality in Cloud Foundry Runtime cf-release before 216, UAA before 2.5.2, and Pivotal Cloud Foundry (PCF) Elastic…39Monitor
- CVE-2017-4992An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v261; UAA release 2.x versions prior to v2.7.4.17, 3.6.x…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2017-4970Jun 13, 2017 · An issue was discovered in Cloud Foundry Foundation cf-release v255 and Staticfile buildpack versions v1.4.0 - v1.4.3.23Monitor
- ← EarlierCVE-2017-4972Jun 13, 2017 · 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…30Monitor
- Later →CVE-2017-4991Jun 13, 2017 · An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v260; UAA release 2.x versions prior to v2.7.4.16, 3.6.x…28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.cloudfoundry.identity:cloudfoundry-identity-server | 2.7.4.15 | Package registry (OSV) |
| Maven:org.cloudfoundry.identity:cloudfoundry-identity-server | 3.16.0 | Package registry (OSV) |
| Maven:org.cloudfoundry.identity:cloudfoundry-identity-server | 3.6.9 | Package registry (OSV) |
| Maven:org.cloudfoundry.identity:cloudfoundry-identity-server | 3.9.11 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.
The bug in code
The whole CWE-89 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = '" + owner + "'"
);Fixed
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = $1",
[owner]
);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Expanding Control over the Operating System from the DatabaseCAPEC-470Very High
- SQL InjectionCAPEC-66likelihood: High · High
- Blind SQL InjectionCAPEC-7likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.