CVE-2015-3191
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWith 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe UAA (User Account and Authentication) server in Cloud Foundry contains a CSRF vulnerability in its change_email form that allows attackers to silently modify a victim's email address by诱骗用户在登录状态下访问恶意链接。此漏洞仅影响使用UAA内部用户存储进行身份验证的部署，通过SAML或LDAP集成的部署不受影响。
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 209<= 1.4.5<= 2.2.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine your UAA versionCheck the UAA server version by accessing the /info endpoint or reviewing your deployment manifest and release notes for the installed UAA componentAffected if The installed UAA version is 2.2.6 or lower, or the Cf Release is 209 or lower, or Elastic Runtime is 1.4.5 or lower
-
Identify your authentication backendReview your UAA configuration file (uaa.yml) or deployment manifest to determine whether authentication is configured using the internal user store, SAML identity provider, or LDAPAffected if The UAA is configured to use its internal user store (uaa) for authentication rather than SAML or LDAP integration
-
Verify the change_email endpoint is accessibleConfirm that the UAA server's change_email form endpoint is accessible to authenticated users in your deploymentAffected if Users authenticated via the internal UAA user store can access and submit the email change form without additional CSRF protection tokens
-
Check UAA security configurationInspect the UAA server's security configuration for CSRF token validation on form submissions, particularly on the /change_email endpointAffected if CSRF protection is not enforced or is missing for the email change functionality
You are affected if your deployment uses Cloud Foundry or UAA at one of the affected versions listed AND uses the internal UAA user store for authentication rather than SAML or LDAP integration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data升级UAA到2.2.6之后的版本，或升级对应的cf-release和Pivotal Cloud Foundry Runtime组件到修复版本，并验证内部用户认证仍然正常工作。
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-3191 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data