Impact
The vulnerability allowed unauthorized access to workspace details due to an insecure API implementation. Instead of deriving the workspaceId from the authenticated user's JWT, the API permitted users to pass a workspaceId as a query parameter, enabling them to access data from other workspaces. This affected all users who had access to the vulnerable API endpoint.
Patches
The issue has been fixed by enforcing strict validation in the API. The workspaceId is now exclusively derived from the JWT token, preventing users from specifying a different workspaceId in the request. Users should upgrade to version to ensure they are protected.
Workarounds
As a temporary mitigation, organizations can implement request validation at the API gateway or middleware level to reject requests containing workspaceId as a query parameter. Additionally, monitoring API logs for suspicious workspace access patterns can help detect unauthorized access attempts.
skdishansachin Reporter
Impact
The vulnerability allowed unauthorized access to workspace details due to an insecure API implementation. Instead of deriving the workspaceId from the authenticated user's JWT, the API permitted users to pass a workspaceId as a query parameter, enabling them to access data from other workspaces. This affected all users who had access to the vulnerable API endpoint.
Patches
The issue has been fixed by enforcing strict validation in the API. The workspaceId is now exclusively derived from the JWT token, preventing users from specifying a different workspaceId in the request. Users should upgrade to version to ensure they are protected.
Workarounds
As a temporary mitigation, organizations can implement request validation at the API gateway or middleware level to reject requests containing workspaceId as a query parameter. Additionally, monitoring API logs for suspicious workspace access patterns can help detect unauthorized access attempts.