CVE Tools
Track your stack

CVE-2017-4974

No known exploitation. EPSS puts it in the 62nd percentile. Fixed in 2.7.4.15.

CVSS 3.16.5MediumEPSS percentile62nd1.0% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix2.7.4.15Upgrade to this build
Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD, GitHub

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • n/a Cloud Foundry UAAAffected: Cloud Foundry UAAUpgrade to: not statedStated by: CVE record
  • Maven org.cloudfoundry.identity:cloudfoundry-identity-serverAffected: ≥ 2.0.0, < 2.7.4.15Upgrade to: 2.7.4.15Stated by: GitHub advisory
  • Cloudfoundry Cf-releaseAffected: ≤ v257Upgrade to: after v257Stated by: NVD
  • Cloudfoundry Cloud Foundry Uaa BoshAffected: ≤ 30Upgrade to: after 30Stated by: NVD
  • Pivotal Software Cloud Foundry UaaAffected: ≤ 4.2.0Upgrade to: after 4.2.0Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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."

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS62nd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.0% chance of exploitation activity in the next 30 days, which ranks it in the 62nd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 3256 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Publishedweakness classified, att&ck mapped

Affected products

And 1 more affected product. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 6.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 8 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Cf-release, not every advisory.