CVE-2016-8218
Last modified
CVE-2016-8218 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.30% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| 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 |
References
- https://www.cloudfoundry.org/cve-2016-8218/Patch, Vendor Advisory
- https://www.cloudfoundry.org/cve-2016-8218/Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-8218?
How severe is CVE-2016-8218?
How do I fix CVE-2016-8218?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-8212An issue was discovered in EMC RSA BSAFE Crypto-J versions p…7.5
- CVE-2016-8213EMC Documentum WebTop Version 6.8, prior to P18 and Version …
- CVE-2016-8214EMC Avamar Data Store (ADS) and Avamar Virtual Edition (AVE)…
- CVE-2016-8215EMC RSA Security Analytics 10.5.3 and 10.6.2 contains fixes …
- CVE-2016-8216EMC Data Domain OS (DD OS) 5.4 all versions, EMC Data Domain…6.7
- CVE-2016-8217EMC RSA BSAFE Crypto-J versions prior to 6.2.2 has a PKCS#12…3.7
- CVE-2016-8219An issue was discovered in Cloud Foundry Foundation cf-relea…6.5
- CVE-2016-8220Pivotal Gemfire for PCF, versions 1.6.x prior to 1.6.5.0 and…
- CVE-2016-8221Privilege Escalation in Lenovo XClarity Administrator earlie…
- CVE-2016-8222A vulnerability has been identified in a signed kernel drive…
- CVE-2016-8223During an internal security review, Lenovo identified a loca…
- CVE-2016-8224A vulnerability has been identified in some Lenovo Notebook …
Are you affected by CVE-2016-8218?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
