CVE-2017-4973: High severity Cloudfoundry Cloud Foundry Uaa Bosh vulnerability

Published Jun 13, 2017
·
Updated

An 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 versions prior to v3.6.8, 3.9.x versions prior to v3.9.10, and other versions prior to v3.15.0; and UAA bosh release (uaa-release) 13.x versions prior to v13.12, 24.x versions prior to v24.7, and other versions prior to v30. A vulnerability has been identified with the groups endpoint in UAA allowing users to elevate their privileges.

Affected Software

62 affected componentsFixes available
maven/org.cloudfoundry.identity:cloudfoundry-identity-server>=3.10.0<3.15.0
3.15.0
maven/org.cloudfoundry.identity:cloudfoundry-identity-server>=3.7.0<3.9.10
3.9.10
maven/org.cloudfoundry.identity:cloudfoundry-identity-server>=3.0.0<3.6.8
3.6.8
maven/org.cloudfoundry.identity:cloudfoundry-identity-server>=2.0.0<2.7.4.14
2.7.4.14
Cloudfoundry Cloud Foundry Uaa Bosh<=30
Cloudfoundry Cloud Foundry Uaa Bosh=13.1
Cloudfoundry Cloud Foundry Uaa Bosh=13.2
Cloudfoundry Cloud Foundry Uaa Bosh=13.3
Cloudfoundry Cloud Foundry Uaa Bosh=13.4
Cloudfoundry Cloud Foundry Uaa Bosh=13.5
Cloudfoundry Cloud Foundry Uaa Bosh=13.6
Cloudfoundry Cloud Foundry Uaa Bosh=13.7
Cloudfoundry Cloud Foundry Uaa Bosh=13.8
Cloudfoundry Cloud Foundry Uaa Bosh=13.9
Cloudfoundry Cloud Foundry Uaa Bosh=13.10
Cloudfoundry Cloud Foundry Uaa Bosh=13.11
Cloudfoundry Cloud Foundry Uaa Bosh=24
Cloudfoundry Cloud Foundry Uaa Bosh=24.1
Cloudfoundry Cloud Foundry Uaa Bosh=24.2
Cloudfoundry Cloud Foundry Uaa Bosh=24.3
Cloudfoundry Cloud Foundry Uaa Bosh=24.4
Cloudfoundry Cloud Foundry Uaa Bosh=24.5
Cloudfoundry Cloud Foundry Uaa Bosh=24.6
Cloudfoundry Cloud Foundry Uaa Bosh=30.1
Cloudfoundry Cloud Foundry Uaa Bosh=30.2
Cloudfoundry Cloud Foundry Uaa Bosh=30.3
Pivotal Software Cloud Foundry Cf<=256
Pivotal Software Cloud Foundry Uaa=2.2.5.4
Pivotal Software Cloud Foundry Uaa=2.7.1
Pivotal Software Cloud Foundry Uaa=2.7.2
Pivotal Software Cloud Foundry Uaa=2.7.3
Pivotal Software Cloud Foundry Uaa=2.7.4
Pivotal Software Cloud Foundry Uaa=2.7.4.1
Pivotal Software Cloud Foundry Uaa=2.7.4.2
Pivotal Software Cloud Foundry Uaa=2.7.4.3
Pivotal Software Cloud Foundry Uaa=2.7.4.4
Pivotal Software Cloud Foundry Uaa=2.7.4.5
Pivotal Software Cloud Foundry Uaa=2.7.4.6
Pivotal Software Cloud Foundry Uaa=2.7.4.7
Pivotal Software Cloud Foundry Uaa=2.7.4.8
Pivotal Software Cloud Foundry Uaa=2.7.4.9
Pivotal Software Cloud Foundry Uaa=2.7.4.11
Pivotal Software Cloud Foundry Uaa=2.7.4.12
Pivotal Software Cloud Foundry Uaa=2.7.4.13
Pivotal Software Cloud Foundry Uaa=3.6.1
Pivotal Software Cloud Foundry Uaa=3.6.2
Pivotal Software Cloud Foundry Uaa=3.6.3
Pivotal Software Cloud Foundry Uaa=3.6.4
Pivotal Software Cloud Foundry Uaa=3.6.5
Pivotal Software Cloud Foundry Uaa=3.6.6
Pivotal Software Cloud Foundry Uaa=3.6.7
Pivotal Software Cloud Foundry Uaa=3.9.1
Pivotal Software Cloud Foundry Uaa=3.9.2
Pivotal Software Cloud Foundry Uaa=3.9.3
Pivotal Software Cloud Foundry Uaa=3.9.4
Pivotal Software Cloud Foundry Uaa=3.9.5
Pivotal Software Cloud Foundry Uaa=3.9.6
Pivotal Software Cloud Foundry Uaa=3.9.7
Pivotal Software Cloud Foundry Uaa=3.9.8
Pivotal Software Cloud Foundry Uaa=3.9.9
Pivotal Software Cloud Foundry Uaa=3.9.12
Pivotal Software Cloud Foundry Uaa=3.9.13

Event History

Jun 13, 2017
CVE Published
via MITRE·06:00 AM
Data Sourced
via MITRE·06:00 AM
DescriptionWeakness
May 13, 2022
Advisory Published
via GitHub·01:07 AM

Frequently Asked Questions

1

What is the severity of CVE-2017-4973?

CVE-2017-4973 has been classified as a medium severity vulnerability.

2

How do I fix CVE-2017-4973?

To fix CVE-2017-4973, update to Cloud Foundry UAA release versions 2.7.4.14, 3.6.8, 3.9.10, or 3.15.0, or higher.

3

What software is affected by CVE-2017-4973?

CVE-2017-4973 affects versions of Cloud Foundry Foundation cf-release prior to v257 and UAA releases noted in the description.

4

Is CVE-2017-4973 exploitable remotely?

Yes, CVE-2017-4973 can be exploited remotely under specific conditions.

5

Are there known workarounds for CVE-2017-4973?

There are no documented workarounds for CVE-2017-4973; updating to a patched version is the recommended mitigation.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203