Skip to content

Auth0-js bypasses CSRF checks

High severity GitHub Reviewed Published Mar 7, 2018 to the GitHub Advisory Database • Updated Jan 9, 2023

Package

npm auth0-js (npm)

Affected versions

< 9.3.0

Patched versions

9.3.0

Description

The Auth0.js library has a vulnerability affecting versions below 9.3 that allows an attacker to bypass the CSRF check from the state parameter if it's missing from the authorization response, leaving the client vulnerable to CSRF attacks.

References

Published to the GitHub Advisory Database Mar 7, 2018
Reviewed Jun 16, 2020
Last updated Jan 9, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.073%
(33rd percentile)

Weaknesses

CVE ID

CVE-2018-7307

GHSA ID

GHSA-wpq7-q8j4-72jg

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.