Description
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 products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
WSO2 WSO2 API Manager
Default version status: unaffected
0 to < 3.2.0unknown3.2.0 to < 3.2.0.434affected3.2.1 to < 3.2.1.54affected4.1.0 to < 4.1.0.218affected4.2.0 to < 4.2.0.156affected4.3.0 to < 4.3.0.67affected4.4.0 to < 4.4.0.30affected4.5.0 to < 4.5.0.14affected
WSO2 WSO2 Universal Gateway
Default version status: unaffected
0 to < 4.5.0unknown4.5.0 to < 4.5.0.14affected
WSO2 WSO2 API Control Plane
Default version status: unaffected
0 to < 4.5.0unknown4.5.0 to < 4.5.0.15affected
WSO2 Forgerock Key Manager Component
Default version status: unknown
1.0.0 to < 1.0.0.3affected1.0.0 to < 1.0.0.4affected1.1.0 to < 1.1.0.2affected1.1.5 to < 1.1.5.3affected1.1.5 to < 1.1.5.4affected