CVE-2020-151257.7HighCWE-209

CVE-2020-15125: Authorization header is not sanitized in an error object in auth0

auth0 · node-auth0

Affected: auth0 node-auth0 · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.5%probability of exploitation in the next 30 days

75th percentile

050100

Higher than 75% of scored CVEs

7.7HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

auth0 · node-auth0< 2.27.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Generation of Error Message Containing Sensitive Information · Information Disclosure
Vendor: auth0
Published: July 2020
Band: Possible (1 to 10%), July 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-15125 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.