Loading HuntDB...
Hunt
Vulnerability Intelligence by wss.sh
Home Daily Briefings High Impact CVEs Recent Exploits KEV Catalog GitHub Advisories Latest Updates Security News
Sign In Sign Up

CVE-2020-15125

HIGH
Published 2020-07-29T16:25:15
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2020-15125. We'll provide specific mitigation strategies based on your environment and risk profile.

CVSS Score

V3.1
7.7
/10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Base Score Metrics
Exploitability: N/A Impact: N/A

EPSS Score

v2025.03.14
0.003
probability
of exploitation in the wild

There is a 0.3% chance that this vulnerability will be exploited in the wild within the next 30 days.

Updated: 2025-06-25
Exploit Probability
Percentile: 0.534
Higher than 53.4% of all CVEs

Attack Vector Metrics

Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
CHANGED

Impact Metrics

Confidentiality
HIGH
Integrity
NONE
Availability
NONE

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

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

auth0

node-auth0

Affected Versions:

< 2.27.1

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed HIGH

Authorization header is not sanitized in an error object in auth0

GHSA-5jpf-pj32-xx53

Advisory 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

Affected Packages

npm auth0
ECOSYSTEM: ≥0 <2.27.1

CVSS Scoring

CVSS Score

7.5

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

References

WEB https://github.com/auth0/node-auth0/security/advisories/GHSA-5jpf-pj32-xx53
ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2020-15125
WEB https://github.com/auth0/node-auth0/pull/507
WEB https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3c
WEB https://github.com/auth0/node-auth0/tree/v2.27.1

Advisory provided by GitHub Security Advisory Database. Published: July 29, 2020, Modified: January 7, 2021

References

https://github.com/auth0/node-auth0/security/advisories/GHSA-5jpf-pj32-xx53
https://github.com/auth0/node-auth0/pull/507
https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3c
https://github.com/auth0/node-auth0/tree/v2.27.1
Published: 2020-07-29T16:25:15
Last Modified: 2024-08-04T13:08:22.304Z
Copied to clipboard!