First published: Tue 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.
Credit: security_alert@emc.com
Affected Software | Affected Version | How to fix |
---|---|---|
Cloud Foundry CF Release | <=203 | |
Cloud Foundry CF Release | =204 | |
Cloud Foundry CF Release | =205 | |
Cloud Foundry CF Release | =206 | |
Cloud Foundry CF Release | =207 | |
Cloud Foundry CF Release | =208 | |
Cloud Foundry CF Release | =209 | |
Cloud Foundry CF Release | =210 | |
Cloud Foundry CF Release | =211 | |
Cloud Foundry CF Release | =212 | |
Cloud Foundry CF Release | =213 | |
Cloud Foundry CF Release | =214 | |
Cloud Foundry CF Release | =215 | |
Cloud Foundry CF Release | =217 | |
Cloud Foundry CF Release | =218 | |
Cloud Foundry CF Release | =219 | |
Cloud Foundry CF Release | =220 | |
Cloud Foundry CF Release | =221 | |
Cloud Foundry CF Release | =222 | |
Cloud Foundry CF Release | =223 | |
Cloud Foundry CF Release | =224 | |
Cloud Foundry CF Release | =225 | |
Cloud Foundry CF Release | =226 | |
Cloud Foundry CF Release | =227 | |
Cloud Foundry CF Release | =228 | |
Cloud Foundry CF Release | =229 | |
Cloud Foundry CF Release | =230 | |
Cloud Foundry CF Release | =231 | |
Pivotal Cloud Foundry Routing Release | <=0.141.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-8218 is considered a high severity vulnerability due to its potential for user impersonation.
To fix CVE-2016-8218, upgrade to routing-release version 0.142.0 or higher, or cf-release version 232 or later.
CVE-2016-8218 affects Cloud Foundry routing-release versions prior to 0.142.0 and cf-release versions 203 to 231.
CVE-2016-8218 allows unprivileged attackers to impersonate other users to the routing API due to incomplete validation logic in JWT libraries.
Yes, CVE-2016-8218 can be exploited relatively easily by attackers who can create a valid JWT.