CVE-2016-6637 — cloudfoundry-identity-ser…
CRITICALCVE-2016-6637 is a critical-severity (CVSS 9.6) Cross-Site Request Forgery (CSRF) vulnerability in org.cloudfoundry.identity:cloudfoundry-identity-server. A fix is available for org.cloudfoundry.identity:cloudfoundry-identity-server — see the affected versions and patch details below.
Cloud Foundry vulnerable to Cross-Site Request Forgery
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2016-6637 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.cloudfoundry.identity:cloudfoundry-identity-server☕org.cloudfoundry.identity:cloudfoundry-identity-server☕org.cloudfoundry.identity:cloudfoundry-identity-server☕org.cloudfoundry.identity:cloudfoundry-identity-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.cloudfoundry.identity:cloudfoundry-identity-server | ≥ 2.0.0&&< 2.7.4.7 | 2.7.4.7org.cloudfoundry.identity:cloudfoundry-identity-server:2.7.4.7 |
| ☕Maven | org.cloudfoundry.identity:cloudfoundry-identity-server | ≥ 3.0.0&&< 3.3.0.5 | 3.3.0.5org.cloudfoundry.identity:cloudfoundry-identity-server:3.3.0.5 |
| ☕Maven | org.cloudfoundry.identity:cloudfoundry-identity-server | ≥ 3.4.0&&< 3.4.4 | 3.4.4org.cloudfoundry.identity:cloudfoundry-identity-server:3.4.4 |
| ☕Maven | org.cloudfoundry.identity:cloudfoundry-identity-server | ≥ 3.5.0&&< 3.7.0 | 3.7.0org.cloudfoundry.identity:cloudfoundry-identity-server:3.7.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.cloudfoundry.identity:cloudfoundry-identity-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.cloudfoundry.identity:cloudfoundry-identity-server to 2.7.4.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-6637 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2016-6637 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2016-6637. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2016-6637 in your dependencies?
O3 Security finds CVE-2016-6637 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.