Username Hash Leak via WebSocket

Description

A potential security issue has been identified where sensitive information, specifically an example hash of {Example context: Example}, was discovered within incoming WebSocket messages. This may suggest that the application is susceptible to an Insecure Direct Object Reference (IDOR) vulnerability. Further manual testing will be necessary to determine whether this discovery can be exploited.

Recommendation

To mitigate this risk, it’s recommended to utilize per-user or session indirect object references. Alternatively, ensure each direct object reference is tied to a robust authorization check to guarantee the user is authorized for the requested object.

Written by

Anandhu Krishnan

Lead Engineer