CVE-2016-8218: Input Validation

Published Jun 13, 2017
·
Updated

An issue was discovered in Cloud Foundry Foundation routing-release versions prior to 0.142.0 and cf-release versions 203 to 231. Incomplete validation logic in JSON Web Token (JWT) libraries can allow unprivileged attackers to impersonate other users to the routing API, aka an "Unauthenticated JWT signing algorithm in routing" issue.

Affected Software

29 affected components
Cloudfoundry Cf-release<=203
Cloudfoundry Cf-release=204
Cloudfoundry Cf-release=205
Cloudfoundry Cf-release=206
Cloudfoundry Cf-release=207
Cloudfoundry Cf-release=208
Cloudfoundry Cf-release=209
Cloudfoundry Cf-release=210
Cloudfoundry Cf-release=211
Cloudfoundry Cf-release=212
Cloudfoundry Cf-release=213
Cloudfoundry Cf-release=214
Cloudfoundry Cf-release=215
Cloudfoundry Cf-release=217
Cloudfoundry Cf-release=218
Cloudfoundry Cf-release=219
Cloudfoundry Cf-release=220
Cloudfoundry Cf-release=221
Cloudfoundry Cf-release=222
Cloudfoundry Cf-release=223
Cloudfoundry Cf-release=224
Cloudfoundry Cf-release=225
Cloudfoundry Cf-release=226
Cloudfoundry Cf-release=227
Cloudfoundry Cf-release=228
Cloudfoundry Cf-release=229
Cloudfoundry Cf-release=230
Cloudfoundry Cf-release=231
Cloudfoundry Routing-release<=0.141.0

Event History

Jun 13, 2017
CVE Published
via MITRE·06:00 AM
Data Sourced
via MITRE·06:00 AM
DescriptionWeakness

Frequently Asked Questions

1

What is the severity of CVE-2016-8218?

CVE-2016-8218 is considered a high severity vulnerability due to its potential for user impersonation.

2

How do I fix CVE-2016-8218?

To fix CVE-2016-8218, upgrade to routing-release version 0.142.0 or higher, or cf-release version 232 or later.

3

Which versions are affected by CVE-2016-8218?

CVE-2016-8218 affects Cloud Foundry routing-release versions prior to 0.142.0 and cf-release versions 203 to 231.

4

What kind of attack does CVE-2016-8218 allow?

CVE-2016-8218 allows unprivileged attackers to impersonate other users to the routing API due to incomplete validation logic in JWT libraries.

5

Is CVE-2016-8218 easily exploitable?

Yes, CVE-2016-8218 can be exploited relatively easily by attackers who can create a valid JWT.

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