Vulnerabilities · 2020 · Auth0
CVE-2020-15125
Auth0.js vulnerability
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 products
Auth0.js. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Auth0.js runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/auth0/node-auth0/pull/507 · Patch
- github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3c · Patch
- github.com/auth0/node-auth0/security/advisories/GHSA-5jpf-pj32-xx53 · Third Party Advisory
- github.com/auth0/node-auth0/tree/v2.27.1 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-15125
- cve.org/CVERecord?id=CVE-2020-15125
More vulnerabilities in Auth0 products
CVE-2022-29172CVE-2022-24794CVE-2022-23541CVE-2022-23540CVE-2022-23539CVE-2022-23505CVE-2021-43812CVE-2021-41246All 34
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.