In auth0 (npm package) versions before 2.27.1, a DenyList of specific keys that should be sanitized from the request object contained in the error object is used. The key for Authorization header is not sanitized and in certain cases the Authorization header value can be logged exposing a bearer token. You are affected by this vulnerability if you are using the auth0 npm package, and you are using a Machine to Machine application authorized to use Auth0's management API
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NAuth0 Auth0.js
APPAuth0< 2.27.1
Related vulnerabilities
The Auth0 authentication service before 2017-10-15 allows privilege escalation because the JWT audience is not...
Auth0.js is a client-side JavaScript library for Auth0. From 8.11.0 to 9.32.0, under specific preconditions, t...
CSRF exists in the Auth0 authentication service through 14591 if the Legacy Lock API flag is enabled.
The Auth0 Auth0.js library before 9.3 has CSRF because it mishandles the case where the authorization response...
A cross-origin vulnerability has been discovered in the Auth0 auth0.js library affecting versions < 8.12. This...