CVE-2020-15125 – auth0

Package

Manager: npm
Name: auth0
Vulnerable Version: >=0 <2.27.1

Severity

Level: High

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

EPSS: 0.00308 pctl0.53473

Details

Authorization header is not sanitized in an error object in auth0 ### Overview Versions before and including `2.27.0` use a block list of specific keys that should be sanitized from the request object contained in the error object. When a request to Auth0 management API fails, the key for `Authorization` header is not sanitized and the `Authorization` header value can be logged exposing a bearer token. ### Am I affected? You are affected by this vulnerability if all of the following conditions apply: - You are using `auth0` npm package - You are using a Machine to Machine application authorized to use Auth0's management API https://auth0.com/docs/flows/concepts/client-credentials ### How to fix that? Upgrade to version `2.27.1` ### Will this update impact my users? The fix provided in patch will not affect your users. ### Credit http://github.com/osdiab

Metadata

Created: 2020-07-29T16:26:22Z
Modified: 2021-01-07T23:44:25Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2020/07/GHSA-5jpf-pj32-xx53/GHSA-5jpf-pj32-xx53.json
CWE IDs: ["CWE-209"]
Alternative ID: GHSA-5jpf-pj32-xx53
Finding: F037
Auto approve: 1