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
Advisories
Source ID Title
EUVD EUVD EUVD-2020-0538 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
Github GHSA Github GHSA GHSA-5jpf-pj32-xx53 Authorization header is not sanitized in an error object in auth0
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2024-08-04T13:08:22.304Z

Reserved: 2020-06-25T00:00:00

Link: CVE-2020-15125

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2020-07-29T17:15:13.577

Modified: 2024-11-21T05:04:52.543

Link: CVE-2020-15125

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.