Skip to content

@clerk/nextjs auth() and getAuth() methods vulnerable to insecure direct object reference (IDOR)

Critical severity GitHub Reviewed Published Jan 12, 2024 in clerk/javascript • Updated Jan 15, 2024

Package

npm @clerk/nextjs (npm)

Affected versions

>= 4.7.0, < 4.29.3

Patched versions

4.29.3

Description

Impact

Unauthorized access or privilege escalation due to a logic flaw in auth() in the App Router or getAuth() in the Pages Router.

Affected Versions

All applications that that use @clerk/nextjs versions in the range of >= 4.7.0,< 4.29.3 in a Next.js backend to authenticate API Routes, App Router, or Route handlers. Specifically, those that call auth() in the App Router or getAuth() in the Pages Router. Only the @clerk/nextjs SDK is impacted. Other SDKs, including other Javascript-based SDKs, are not impacted.

Patches

Fix included in @clerk/nextjs@4.29.3.

References

References

@zythosec zythosec published to clerk/javascript Jan 12, 2024
Published by the National Vulnerability Database Jan 12, 2024
Published to the GitHub Advisory Database Jan 12, 2024
Reviewed Jan 12, 2024
Last updated Jan 15, 2024

Severity

Critical

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
High
Privileges required
None
User interaction
None
Scope
Changed
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.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

EPSS score

0.065%
(30th percentile)

Weaknesses

CVE ID

CVE-2024-22206

GHSA ID

GHSA-q6w5-jg5q-47vg

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.