CVE Tools
Track your stack

CVE-2015-3189

No known exploitation. EPSS puts it in the 58th percentile. Fixed in 2.2.5.

CVSS 3.13.7LowEPSS percentile58th0.8% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix2.2.5Upgrade 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.

  • Pivotal Cloud FoundryAffected: Runtime cf-release versions v208 or earlierUpgrade to: not statedAffected: UAA Standalone versions 2.2.5 or earlierUpgrade to: not statedAffected: Runtime 1.4.5 or earlierUpgrade to: not statedStated by: CVE record
  • Maven org.cloudfoundry.identity:cloudfoundry-identity-serverAffected: < 2.2.5Upgrade to: 2.2.5Stated by: GitHub advisory
  • Cloudfoundry Cf-releaseAffected: ≤ 208Upgrade to: after 208Stated by: NVD
  • Pivotal Software Cloud Foundry Elastic RuntimeAffected: ≤ 1.4.5Upgrade to: after 1.4.5Stated by: NVD
  • Pivotal Software Cloud Foundry UaaAffected: ≤ 2.2.5Upgrade to: after 2.2.5Stated by: NVD

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

What it is

From the CVE record

With Cloud Foundry Runtime cf-release versions v208 or earlier, UAA Standalone versions 2.2.5 or earlier and Pivotal Cloud Foundry Runtime 1.4.5 or earlier, old Password Reset Links are not expired after the user changes their current email address to a new one. This vulnerability is applicable only when using the UAA internal user store for authentication. Deployments enabled for integration via SAML or LDAP are not affected.

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.

EPSS58th
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

0.8% chance of exploitation activity in the next 30 days, which ranks it in the 58th percentile of scored CVEs.

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

Lifecycle

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

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

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 3.7 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • 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 4 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 Pivotal Software, not every advisory.