Skip to content

Authorization header is not sanitized in an error object in auth0

High severity GitHub Reviewed Published Jul 28, 2020 in auth0/node-auth0 • Updated Jan 9, 2023

Package

npm auth0 (npm)

Affected versions

< 2.27.1

Patched versions

2.27.1

Description

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:

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

References

@lzychowski lzychowski published to auth0/node-auth0 Jul 28, 2020
Reviewed Jul 29, 2020
Published to the GitHub Advisory Database Jul 29, 2020
Last updated Jan 9, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS score

0.092%
(40th percentile)

Weaknesses

CVE ID

CVE-2020-15125

GHSA ID

GHSA-5jpf-pj32-xx53

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.