Description
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
Remediation
References
https://github.com/auth0/node-auth0/pull/507
https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3c
https://github.com/auth0/node-auth0/security/advisories/GHSA-5jpf-pj32-xx53
https://github.com/auth0/node-auth0/tree/v2.27.1
Related Vulnerabilities
CVE-2022-43407 Vulnerability in maven package org.jenkins-ci.plugins:pipeline-input-step
CVE-2022-23622 Vulnerability in maven package org.xwiki.platform:xwiki-platform-web-templates
CVE-2020-28271 Vulnerability in npm package deephas
CVE-2021-25930 Vulnerability in maven package org.opennms:opennms-webapp