Advisories for Npm/Auth0-Js package

Under specific preconditions, the Auth0.js SDK may improperly return user profile information using a valid access token when a specifically crafted invalid ID token is provided.

In auth0 (npm package), a DenyList of specific keys that should be sanitized from the request object contained in the error object is used. and you are using a Machine to Machine application authorized to use Auth0's management API.

In the case of an (authentication) error, the error object returned by the library contains the original request of the user, which may include the plaintext password the user entered. If the error object is exposed or logged without modification, the application risks password exposure.

The Auth0 authentication service allows privilege escalation because the JWT audience field is not validated.

CSRF exists in the Auth0 authentication service when the Legacy Lock API flag is enabled.

The Auth0 Authjs library has CSRF because it mishandles the case where the authorization response lacks the state parameter.

A cross-origin vulnerability has been discovered in auth0. This vulnerability allows an attacker to acquire authenticated user tokens and invoke services on a user's behalf if the target site or application uses a popup callback page with auth0.popup.callback().