Advisory

GHSA-5jpf-pj32-xx53

Also known as: CVE-2020-15125

Summary

Authorization header is not sanitized in an error object in auth0

Details

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

Severity

High Basis: The source's own band: HIGH

Dates

Published
2020-07-29 16:26 UTC
Modified
2026-05-04 08:46 UTC

Affected packages and fixes

auth0

npm · All systems

Affected

  • introduced 0, fixed 2.27.1 (semver)

Fixed versions

2.27.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences