Improper Token Revocation via Session-Bound Token Flow in Multiple WSO2 Products Allows Unauthorized Access After Session Termination
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in API Control Plane 4.5.0.47, API Control Plane 4.6.0.13, API Manager 3.1.0.352 and 37 more.
Tokens associated with user sessions are not revoked when the corresponding user session is terminated, unless another SSO request is initiated. This occurs when the session-bound token feature is enabled with token binding validation and the "Revoke token upon user logout" option is not active. The software fails to automatically invalidate session-bound tokens upon user session termination. This vulnerability exists when token binding validation is enabled. As a result, a malicious actor possessing a valid session-bound token could exploit this condition to maintain unauthorized access to applications and resources even after the associated user session has ended, potentially leading to the exposure of sensitive user data.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| WSO2 | API Control Plane | >=4.5.0 <4.5.0.47, >=4.6.0 <4.6.0.13 | 4.5.0.47, 4.6.0.13 |
| WSO2 | API Manager | >=3.1.0 <3.1.0.352, >=3.2.0 <3.2.0.456, >=3.2.1 <3.2.1.81, >=4.0.0 <4.0.0.376, >=4.1.0 <4.1.0.246, >=4.2.0 <4.2.0.186, >=4.3.0 <4.3.0.97, >=4.4.0 <4.4.0.61, >=4.5.0 <4.5.0.46, >=4.6.0 <4.6.0.11 | 3.1.0.352, 3.2.0.456, 3.2.1.81, 4.0.0.376, 4.1.0.246, 4.2.0.186, 4.3.0.97, 4.4.0.61, 4.5.0.46, 4.6.0.11 |
| WSO2 | Carbon OAuth | >=6.11.21 <6.11.21.94, >=6.13.16 <6.13.16.21, >=6.13.19 <6.13.19.14, >=6.13.27 <6.13.27.10, >=6.13.41 <6.13.41.1, >=6.4.111 <6.4.111.165, >=6.4.176 <6.4.176.30, >=6.4.180 <6.4.180.14, >=6.4.2 <6.4.2.171, >=6.8.0 <6.8.0.54, >=6.9.6 <6.9.6.29, >=7.0.259 <7.0.259.34, >=7.0.26 <7.0.26.87, >=7.0.385 <7.0.385.3 | 6.11.21.94, 6.13.16.21, 6.13.19.14, 6.13.27.10, 6.13.41.1, 6.4.111.165, 6.4.176.30, 6.4.180.14, 6.4.2.171, 6.8.0.54, 6.9.6.29, 7.0.259.34, 7.0.26.87, 7.0.385.3 |
| WSO2 | Identity Server | >=5.10.0 <5.10.0.372, >=5.10.0 <5.10.0.381, >=5.11.0 <5.11.0.428, >=6.0.0 <6.0.0.255, >=6.1.0 <6.1.0.256, >=7.0.0 <7.0.0.133, >=7.1.0 <7.1.0.41, >=7.2.0 <7.2.0.3 | 5.10.0.372, 5.10.0.381, 5.11.0.428, 6.0.0.255, 6.1.0.256, 7.0.0.133, 7.1.0.41, 7.2.0.3 |
| WSO2 | Open Banking AM | >=2.0.0 <2.0.0.401 | 2.0.0.401 |
| WSO2 | Open Banking IAM | >=2.0.0 <2.0.0.421 | 2.0.0.421 |
| WSO2 | Traffic Manager | >=4.5.0 <4.5.0.45, >=4.6.0 <4.6.0.11 | 4.5.0.45, 4.6.0.11 |
| WSO2 | Universal Gateway | >=4.5.0 <4.5.0.46, >=4.6.0 <4.6.0.11 | 4.5.0.46, 4.6.0.11 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in WSO2, strongest first
Embed
A live severity badge for an advisory, README or ticket