Multiple cross-site request forgery (CSRF) vulnerabilities in Pivotal Cloud Foundry (PCF) before 242; UAA 2.x before 2.7.4.7, 3.x before 3.3
Multiple cross-site request forgery (CSRF) vulnerabilities in Pivotal Cloud Foundry (PCF) before 242; UAA 2.x before 2.7.4.7, 3.x before 3.3.0.5, and 3.4.x before 3.4.4; UAA BOSH before 11.5 and 12.x before 12.5; Elastic Runtime before 1.6.40, 1.7.x before 1.7.21, and 1.8.x before 1.8.2; and Ops Manager 1.7.x before 1.7.13 and 1.8.x before 1.8.1 allow remote attackers to hijack the authentication of unspecified victims for requests that approve or deny a scope via a profile or authorize approval page.
- Published
- Sep 29, 2016
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 52th percentile
- CWE
- CWE-352
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
38
Monitor
Low priority for now.
- CVSS
- 38 / 40 · 9.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| cloudfoundry | cloud foundry uaa bosh | cpe:2.3:a:cloudfoundry:cloud_foundry_uaa_bosh |
| pivotal software | cloud foundry | cpe:2.3:a:pivotal_software:cloud_foundry |
| pivotal software | cloud foundry elastic runtime | cpe:2.3:a:pivotal_software:cloud_foundry_elastic_runtime |
| pivotal software | cloud foundry ops manager | cpe:2.3:a:pivotal_software:cloud_foundry_ops_manager |
| pivotal software | cloud foundry uaa | cpe:2.3:a:pivotal_software:cloud_foundry_uaa |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- cloudfoundry cloud foundry uaa boshup to 15.0 inclusive
- pivotal software cloud foundryup to 241 inclusive
- pivotal software cloud foundry elastic runtime1.6.0
- pivotal software cloud foundry elastic runtime1.6.1
- pivotal software cloud foundry elastic runtime1.6.10
- pivotal software cloud foundry elastic runtime1.6.11
- pivotal software cloud foundry elastic runtime1.6.12
- pivotal software cloud foundry elastic runtime1.6.13
- pivotal software cloud foundry elastic runtime1.6.14
- pivotal software cloud foundry elastic runtime1.6.15
- pivotal software cloud foundry elastic runtime1.6.17
- pivotal software cloud foundry elastic runtime1.6.18
- pivotal software cloud foundry elastic runtime1.6.19
- pivotal software cloud foundry elastic runtime1.6.2
- pivotal software cloud foundry elastic runtime1.6.20
- pivotal software cloud foundry elastic runtime1.6.21
- pivotal software cloud foundry elastic runtime1.6.22
- pivotal software cloud foundry elastic runtime1.6.23
- pivotal software cloud foundry elastic runtime1.6.25
- pivotal software cloud foundry elastic runtime1.6.26
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.cloudfoundry.identity:cloudfoundry-identity-server | from 2.0.0 · before 2.7.4.7 | 2.7.4.7 |
| Maven | org.cloudfoundry.identity:cloudfoundry-identity-server | from 3.0.0 · before 3.3.0.5 | 3.3.0.5 |
| Maven | org.cloudfoundry.identity:cloudfoundry-identity-server | from 3.4.0 · before 3.4.4 | 3.4.4 |
| Maven | org.cloudfoundry.identity:cloudfoundry-identity-server | from 3.5.0 · before 3.7.0 | 3.7.0 |
Same product
cloudfoundry: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-4468SQL injection vulnerability in Pivotal Cloud Foundry (PCF) before 238; UAA 2.x before 2.7.4.4, 3.x before 3.3.0.2, and 3.4.x before 3.4.1; U36Monitor
- CVE-2016-6651The UAA /oauth/token endpoint in Pivotal Cloud Foundry (PCF) before 243; UAA 2.x before 2.7.4.8, 3.x before 3.3.0.6, and 3.4.x before 3.4.5;36Monitor
- CVE-2017-4973An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v257; UAA release 2.x versions prior to v2.7.4.14, 3.6.x ve35Monitor
- CVE-2016-3084The UAA reset password flow in Cloud Foundry release v236 and earlier versions, UAA release v3.3.0 and earlier versions, all versions of Log32Monitor
- CVE-2016-6659Cloud Foundry before 248; UAA 2.x before 2.7.4.12, 3.x before 3.6.5, and 3.7.x through 3.9.x before 3.9.3; and UAA bosh release (aka uaa-rel32Monitor
- CVE-2017-4994An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v263; UAA release 2.x versions prior to v2.7.4.18, 3.6.x ve30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.cloudfoundry.identity:cloudfoundry-identity-server | 2.7.4.7 | Package registry (OSV) |
| Maven:org.cloudfoundry.identity:cloudfoundry-identity-server | 3.3.0.5 | Package registry (OSV) |
| Maven:org.cloudfoundry.identity:cloudfoundry-identity-server | 3.4.4 | Package registry (OSV) |
| Maven:org.cloudfoundry.identity:cloudfoundry-identity-server | 3.7.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.