CVE-2015-3191
No known exploitation. EPSS puts it in the 42nd percentile. A vendor fix is available.
No public exploit knownFixVendor fixNo build named by the sources
No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.
What to do
The vendor has published a fix. Version details are below where the sources state them.
- Pivotal Cloud FoundryAffected: Runtime cf-release versions v209 or earlierUpgrade to: not statedAffected: UAA Standalone versions 2.2.6 or earlierUpgrade to: not statedAffected: Runtime 1.4.5 or earlierUpgrade to: not statedStated by: CVE record
- Cloudfoundry Cf-releaseAffected: ≤ 209Upgrade to: after 209Stated 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.6Upgrade to: after 2.2.6Stated 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 v209 or earlier, UAA Standalone versions 2.2.6 or earlier and Pivotal Cloud Foundry Runtime 1.4.5 or earlier the change_email form in UAA is vulnerable to a CSRF attack. This allows an attacker to trigger an e-mail change for a user logged into a cloud foundry instance via a malicious link on a attacker controlled site. 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.
- 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.5% chance of exploitation activity in the next 30 days, which ranks it in the 42nd 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.
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Scored 8.8 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 NoneNo authentication required — anyone can exploit this
- User Interaction RequiredA user must click a link, open a file, or perform some action
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 HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Initial AccessT1189Drive-by Compromisemedium confidence
Sources
References in the record
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.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI