CVE-2020-15125
The key for Authorization header is not sanitized and in certain cases the Authorization header value can be logged exposing a bearer token.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.54%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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
- CVSS 3.1
- 7.7 HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- EPSS
- 1.54% probability · 73th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-209
- Affected
- auth0/auth0.js
- Source
- security-advisories@github.com
References
- https://github.com/auth0/node-auth0/pull/507Patch, Third Party Advisory
- https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3cPatch, Third Party Advisory
- https://github.com/auth0/node-auth0/security/advisories/GHSA-5jpf-pj32-xx53Third Party Advisory
- https://github.com/auth0/node-auth0/tree/v2.27.1Release Notes, Third Party Advisory
- https://github.com/auth0/node-auth0/pull/507Patch, Third Party Advisory
- https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3cPatch, Third Party Advisory
- https://github.com/auth0/node-auth0/security/advisories/GHSA-5jpf-pj32-xx53Third Party Advisory
- https://github.com/auth0/node-auth0/tree/v2.27.1Release Notes, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.