Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

auth0

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.7npmAmendedPublished

    Authorization header is not sanitized in an error object in auth0

    CVE-2020-15125 · GHSA-5jpf-pj32-xx53

    Affected
    • npm auth0 < 2.27.1
    Fixed in
    2.27.1· Vendor fix available
    Issue
    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

    Recommended action: Upgrade to 2.27.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →