CVE-2020-15125 Authorization header is not sanitized in an error object in auth0
Attackers can obtain bearer tokens from logs if the auth0 npm library is used in specific machine-to-machine configurations.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-15125?
CVE-2020-15125 is a high-severity vulnerability in node-auth0, published on 29 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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
Weakness: CWE-209
Which versions are affected by CVE-2020-15125?
2 open source packages ship an affected version, including auth0. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
auth0 npm | All versions | 2.27.1 |
auth0 npm | All versions | 2.27.1 |
Products include Auth0 Auth0.js.
How do I fix CVE-2020-15125?
Upgrade auth0 to 2.27.1 or later.
Is CVE-2020-15125 being exploited?
There is no known exploitation of CVE-2020-15125 in the wild and no public exploit code.
Other vulnerabilities in node-auth0
Sources
Also known as GHSA-5jpf-pj32-xx53.