NextAuth.js up to 3.29.4/4.4.x URL callbackUrl unusual condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in NextAuth.js up to 3.29.4/4.4.x. It has been declared as problematic. This issue affects some unknown processing of the component URL Handler. The manipulation of the argument callbackUrl results in unusual condition. This vulnerability is identified as CVE-2022-31093. The attack can be executed remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in NextAuth.js up to 3.29.4/4.4.x (JavaScript Library). It has been classified as problematic. Affected is some unknown processing of the component URL Handler. The manipulation of the argument callbackUrl with an unknown input leads to a unusual condition vulnerability. CWE is classifying the issue as CWE-754. The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. This is going to have an impact on availability. CVE summarizes:
NextAuth.js is a complete open source authentication solution for Next.js applications. In affected versions an attacker can send a request to an app using NextAuth.js with an invalid `callbackUrl` query parameter, which internally is converted to a `URL` object. The URL instantiation would fail due to a malformed URL being passed into the constructor, causing it to throw an unhandled error which led to the **API route handler timing out and logging in to fail**. This has been remedied in versions 3.29.5 and 4.5.0. If for some reason you cannot upgrade, the workaround requires you to rely on Advanced Initialization. Please see the documentation for more.
The weakness was released 06/28/2022 as GHSA-g5fm-jp9v-2432. The advisory is available at github.com. This vulnerability is traded as CVE-2022-31093 since 05/18/2022. Technical details are known, but there is no available exploit.
Upgrading to version 3.29.5 or 4.5.0 eliminates this vulnerability. Applying the patch 25517b73153332d948114bacdff3b5908de91d85 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Unusual conditionCWE: CWE-754
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: NextAuth.js 3.29.5/4.5.0
Patch: 25517b73153332d948114bacdff3b5908de91d85
Timeline
05/18/2022 🔍06/28/2022 🔍
06/28/2022 🔍
07/16/2022 🔍
Sources
Advisory: GHSA-g5fm-jp9v-2432Status: Confirmed
CVE: CVE-2022-31093 (🔍)
GCVE (CVE): GCVE-0-2022-31093
GCVE (VulDB): GCVE-100-202866
Entry
Created: 06/28/2022 08:22Updated: 07/16/2022 08:44
Changes: 06/28/2022 08:22 (53), 07/16/2022 08:44 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.