CVE-2020-15125

Authorization header is not sanitized in an error object in auth0

HIGH
7.7
CVSS Score
Published: July 29, 2020 at 04:25 PM UTC
Updated: June 17, 2026 at 02:56 AM UTC
1 product affected across 1 vendorAuth0.js

Using node-auth0 by auth0?

Get instant alerts when new vulnerabilities affect node-auth0 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.7
Exploit prediction
EPSS 2%

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.27.1
Affected range stops below 2.27.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

7.7HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-209

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card