Quick answers
- Is CVE-2018-7307 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2018-7307 being exploited in the wild.
- How severe is CVE-2018-7307?
- Low severity, with a CVSS score of 3, published 7 March 2018.
- Which products and versions are affected?
- auth0-js (npm) SEMVER:introduced=0,fixed=9.3.0.
- Is there a fix for CVE-2018-7307?
- Yes. auth0-js (npm): upgrade to 9.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2018-7307 attacked?
- It is attacked over the network.
- Am I affected by CVE-2018-7307?
- Check whether you run auth0-js (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- auth0-js (npm): upgrade to 9.3.0 or later
npm install auth0-js@9.3.0
Technical details
The vulnerability is a CSRF bypass (CWE-352) in auth0-js versions prior to 9.3 where the state parameter validation is not enforced when the state is missing from the authorization response. An attacker can craft a malicious redirect that omits the state parameter, bypassing the client's CSRF protection check. The vulnerability requires user interaction (the user must click a malicious link or be redirected to an attacker-controlled site). By exploiting this, an attacker can execute unintended authentication flows and potentially gain unauthorized access to user accounts. The fix is available in version 9.3.0 and later.
Affected products
- Auth0 auth0-js below 9.3
Identifiers
- CVE-2018-7307
- GHSA-wpq7-q8j4-72jg
Timeline
- 2018-03-07: disclosed
- 2018-03: patched: Fix released in version 9.3.0