GHSA-5jpf-pj32-xx53

Suggest an improvement
Source
https://github.com/advisories/GHSA-5jpf-pj32-xx53
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2020/07/GHSA-5jpf-pj32-xx53/GHSA-5jpf-pj32-xx53.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-5jpf-pj32-xx53
Aliases
Published
2020-07-29T16:26:22Z
Modified
2026-05-04T08:46:05.262794424Z
Severity
  • 7.7 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N CVSS Calculator
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

Database specific 
{
    "cwe_ids": [
        "CWE-209"
    ],
    "github_reviewed_at": "2020-07-29T16:25:59Z",
    "github_reviewed": true,
    "severity": "HIGH",
    "nvd_published_at": null
}
References

Affected packages

npm / auth0

Package

Name
auth0
View open source insights on deps.dev
Purl
pkg:npm/auth0

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.27.1

Database specific

source 
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2020/07/GHSA-5jpf-pj32-xx53/GHSA-5jpf-pj32-xx53.json"