Refresh Token Misuse via Validation Flaw in Multiple WSO2 Products Enables Unauthorized Resource Consumption
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.15, API Manager 4.2.0.156, API Manager 4.3.0.67 and 11 more.
The ForgeRock client fails to correctly validate refresh tokens. This allows a refresh token to be treated as a valid access token, enabling its use for consuming protected resources. This bypasses the intended security control that requires valid client credentials in addition to a refresh token to obtain a new access token. An attacker who obtains a stolen or exposed refresh token can leverage this vulnerability to directly access protected resources. This is possible because the standard security flow requiring client credentials to exchange a refresh token for an access token is circumvented.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| WSO2 | API Control Plane | >=4.5.0 <4.5.0.15 | 4.5.0.15 |
| WSO2 | API Manager | >=4.2.0 <4.2.0.156, >=4.3.0 <4.3.0.67, >=4.4.0 <4.4.0.30, >=4.5.0 <4.5.0.14, >=3.2.0 <3.2.0.434, >=4.1.0 <4.1.0.218, >=3.2.1 <3.2.1.54 | 4.2.0.156, 4.3.0.67, 4.4.0.30, 4.5.0.14, 3.2.0.434, 4.1.0.218, 3.2.1.54 |
| WSO2 | Forgerock Key Manager Component | >=1.0.0 <1.0.0.3, >=1.0.0 <1.0.0.4, >=1.1.0 <1.1.0.2, >=1.1.5 <1.1.5.3, >=1.1.5 <1.1.5.4 | 1.0.0.3, 1.0.0.4, 1.1.0.2, 1.1.5.3, 1.1.5.4 |
| WSO2 | Universal Gateway | >=4.5.0 <4.5.0.14 | 4.5.0.14 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in WSO2, strongest first
Embed
A live severity badge for an advisory, README or ticket