CVE-2020-15125
Last modified
CVE-2020-15125 is a high-severity vulnerability rated 7.7/10 on the CVSS scale. 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. EPSS estimates a 1.54% chance of exploitation in the next 30 days.
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
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Auth0 | Auth0.Js | < 2.27.1 |
References
- https://github.com/auth0/node-auth0/pull/507Patch, Third Party Advisory
- https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3cPatch, Third Party Advisory
- https://github.com/auth0/node-auth0/security/advisories/GHSA-5jpf-pj32-xx53Third Party Advisory
- https://github.com/auth0/node-auth0/tree/v2.27.1Release Notes, Third Party Advisory
- https://github.com/auth0/node-auth0/pull/507Patch, Third Party Advisory
- https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3cPatch, Third Party Advisory
- https://github.com/auth0/node-auth0/security/advisories/GHSA-5jpf-pj32-xx53Third Party Advisory
- https://github.com/auth0/node-auth0/tree/v2.27.1Release Notes, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-15125?
How severe is CVE-2020-15125?
How do I fix CVE-2020-15125?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2020
- CVE-2020-15119In auth0-lock versions before and including 11.25.1, dangero…5.4
- CVE-2020-1512An information disclosure vulnerability exists when the Wind…7.8
- CVE-2020-15120In "I hate money" before version 4.1.5, an authenticated mem…4.9
- CVE-2020-15121In radare2 before version 4.5.0, malformed PDB file names in…9.6
- CVE-2020-15123In codecov (npm package) before version 3.7.1 the upload met…9.3
- CVE-2020-15124In Goobi Viewer Core before version 4.8.3, a path traversal …6.5
- CVE-2020-15126In parser-server from version 3.5.0 and before 4.3.0, an aut…6.5
- CVE-2020-15127In Contour ( Ingress controller for Kubernetes) before versi…7.5
- CVE-2020-15128In OctoberCMS before version 1.0.468, encrypted cookie value…6.3
- CVE-2020-15129In Traefik before versions 1.7.26, 2.2.8, and 2.3.0-rc3, the…4.7
- CVE-2020-1513An elevation of privilege vulnerability exists when the Wind…7.8
- CVE-2020-15130In SLPJS (npm package slpjs) before version 0.27.4, there is…7.5
Are you affected by CVE-2020-15125?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
