Kris Hardy

**Name of the Vulnerable Software and Affected Versions** react-adal versions prior to 0.5.1 **Description** The issue arises from how the nonce, session, and refresh values are stored in the browser local storage or session storage. Each key is automatically appended by '||'. When the received nonce and session keys are generated, the list of values is stored in the browser storage, separated by '||', with '||' always appended to the end of the list. Since '||' will always be the last 2 characters of the stored values, an empty string ("") will always be in the list of the valid values. Therefore, if an empty session parameter is provided in the callback URL, and a specially-crafted JWT token contains an nonce value of "" (empty string), then adal.js will consider the JWT token as authentic. **Recommendations** For versions prior to 0.5.1, update to version 0.5.1 or later to resolve the issue. As a temporary workaround, consider restricting the use of the vulnerable component until a patch is available. Avoid using an empty session parameter in the callback URL and ensure that JWT tokens do not contain an empty string as the nonce value.