User impersonation via unverified cookie JWT claims
Published Jan 12, 2024 · Updated Nov 14, 2024
Authorization bypass in Clerk JavaScript SDK 4.7.0 through 4.29.2 allows remote attackers to impersonate users via crafted JWTs. The @clerk/nextjs endpoint handler reads JWT claims from a cookie before the header, although middleware verified only the header JWT. Applications are exposed only when a Next.js backend calls auth() in the App Router or getAuth() in the Pages Router, enabling arbitrary user identity or role claims.
Summary
What happened
Authorization bypass in Clerk JavaScript SDK 4.7.0 through 4.29.2 allows remote attackers to impersonate users via crafted JWTs. The @clerk/nextjs endpoint handler reads JWT claims from a cookie before the header, although middleware verified only the header JWT. Applications are exposed only when a Next.js backend calls auth() in the App Router or getAuth() in the Pages Router, enabling arbitrary user identity or role claims.
The record
- CVE
- CVE-2024-22206
- Published
- Jan 12, 2024
- Updated
- Nov 14, 2024
- Vendor
- Clerk
- Product
- Clerk JavaScript SDK
- Classifications
- CWE-639, CWE-284, CWE-287, T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 14, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.7.0, < 4.29.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo