How severe is CVE-2015-5170?

CVE-2015-5170 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2015-5170?

CVE-2015-5170 affects the following packages: org.cloudfoundry.identity:cloudfoundry-identity-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-5170?

Update org.cloudfoundry.identity:cloudfoundry-identity-server to 2.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-5170 is resolved across your whole dependency graph.

How do I detect CVE-2015-5170 in my Maven dependencies?

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.

How do I mitigate CVE-2015-5170 if there is no patch (or I can't update yet)?

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.

Is CVE-2015-5170 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-5170 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2015-5170?

CVE-2015-5170 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2015-5170?

CVE-2015-5170 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-5170 published, and has it been updated?

CVE-2015-5170 was published on May 13, 2022 and was last updated on February 28, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2015-5170 — cloudfoundry-identity-ser…

HIGHFix: cloudfoundry/uaa@41dba9d

CVE-2015-5170 is a high-severity (CVSS 8.8) 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 Runtime Cross-Site Request Forgery vulnerability

Published

May 13, 2022

Updated

Feb 28, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.cloudfoundry.identity:cloudfoundry-identity-server

Real-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

Cloud Foundry Runtime cf-release before 216, UAA before 2.5.2, and Pivotal Cloud Foundry (PCF) Elastic Runtime before 1.7.0 allow remote attackers to conduct cross-site request forgery (CSRF) attacks on PWS and log a user into an arbitrary account by leveraging lack of CSRF checks.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.cloudfoundry.identity:cloudfoundry-identity-server`	all versions	2.5.2`org.cloudfoundry.identity:cloudfoundry-identity-server:2.5.2`

Affected Products

3 products · 3 configurations

Application

cf-releasecloudfoundry

< 216

range

Application

cloud foundry elastic runtimepivotal_software

< 1.7.0

range

Application

cloud foundry uaapivotal_software

< 2.5.2

range

Detection & mitigation playbook

Open-source dependency

Detect
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.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-5170 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-5170 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

uaa

7.0/10

Code-Review10/10

Maintained10/10

Branch-ProtectionN/A

Assessed Nov 2, 2026

Timeline

Disclosed

May 13, 2022

Last updated

Feb 28, 2024

Identifiers

CVE-2015-5170

References

Advisorynvd.nist.gov · CVE 2015 5170 Webgithub.com · 41dba9d81dbdf24ede4fb9719de28b1b88b3e1b4 Webgithub.com · a54f3fb8225ef7d5021ca7d4fb52bef1e884568e Webgithub.com · bdb1a39a1e72f615f2e7a429a896a11e7ee5ec17 Webpivotal.io · cve 2015 5170 5173 Websecurityfocus.com Packagegithub.com · uaa

Related vulnerabilities

This CVE is high severity; 4 of 8 other CVEs affecting cloudfoundry-identity-server are rated as high or higher (top: critical).

CVE-2026-22723CVE-2016-5016CVE-2018-1192CVE-2018-11041CVE-2018-15761CVE-2016-6637CVE-2018-1262CVE-2017-8032

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 28, 2024

CVE-2015-5170 — cloudfoundry-identity-ser…

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2015-5170 in your dependencies?