First published: Tue Oct 24 2017(Updated: )
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.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.cloudfoundry.identity:cloudfoundry-identity-server | <2.5.2 | 2.5.2 |
Cloud Foundry CF Release | <216 | |
Pivotal Cloud Foundry Elastic Runtime | <1.7.0 | |
Cloud Foundry User Account and Authentication (UAA) | <2.5.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-5170 has a medium severity rating due to its potential for cross-site request forgery attacks.
To fix CVE-2015-5170, upgrade Cloud Foundry Runtime to version 216 or higher, UAA to version 2.5.2 or higher, and Pivotal Cloud Foundry Elastic Runtime to version 1.7.0 or higher.
CVE-2015-5170 affects Cloud Foundry Runtime versions prior to 216, UAA versions prior to 2.5.2, and Pivotal Cloud Foundry Elastic Runtime versions prior to 1.7.0.
CVE-2015-5170 allows remote attackers to conduct cross-site request forgery (CSRF) attacks.
Yes, CVE-2015-5170 poses a risk to user data as attackers can log a user into an arbitrary account.