CVE-2024-22206: @clerk/nextjs auth() and getAuth() methods vulnerable to insecure direct object reference (IDOR)

Published Jan 12, 2024
·
Updated

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 - https://clerk.com/changelog/2024-01-12 - https://github.com/clerk/javascript/releases/tag/%40clerk%2Fnextjs%404.29.3

Other sources

Clerk helps developers build user management. Unauthorized access or privilege escalation due to a logic flaw in auth() in the App Router or getAuth() in the Pages Router. This vulnerability was patched in version 4.29.3.

MITRE

Affected Software

2 affected componentsFixes available
npm/@clerk/nextjs>=4.7.0<4.29.3
4.29.3
Clerk Javascript Node.js>=4.7.0<4.29.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@clerk/nextjs to a version that resolves this vulnerability.

    Fixed in 4.29.3
  2. Upgrade

    Upgrade @clerk/nextjs to a version that resolves this vulnerability.

    Fixed in 4.29.3
  3. Compensating control

    For Next.js backends using @clerk/nextjs versions in the range >= 4.7.0 and < 4.29.3, ensure API routes, App Router, and route handlers that rely on auth() (App Router) or getAuth() (Pages Router) are not exposed to unauthorized users until upgraded to @clerk/nextjs 4.29.3.

Event History

Jan 12, 2024
CVE Published
via MITRE·08:07 PM
Data Sourced
via MITRE·08:07 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·08:27 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-22206?

The severity of CVE-2024-22206 is high due to the potential for unauthorized access or privilege escalation.

2

How do I fix CVE-2024-22206?

To fix CVE-2024-22206, you should upgrade the @clerk/nextjs package to version 4.29.3 or later.

3

Which versions are affected by CVE-2024-22206?

CVE-2024-22206 affects all versions of @clerk/nextjs in the range of 4.7.0 to 4.29.2.

4

What causes CVE-2024-22206?

CVE-2024-22206 is caused by a logic flaw in the auth() function in the App Router or getAuth() function in the Pages Router.

5

Who is affected by CVE-2024-22206?

Any applications using the affected versions of @clerk/nextjs in a Next.js backend are vulnerable to CVE-2024-22206.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203