Refresh-token disclosure via debug console logging
Published Nov 5, 2024 · Updated Nov 5, 2024
Sensitive-data exposure in WorkOS AuthKit Next.js before 0.13.2 allows local users to read refresh tokens from console logs. In updateSession, debug logging passes session.refreshToken and the newly returned refreshToken directly to console.log during token renewal. The disabled-by-default debug flag must be enabled and a session refresh must occur; access to the resulting logs exposes reusable authentication material.
Summary
What happened
Sensitive-data exposure in WorkOS AuthKit Next.js before 0.13.2 allows local users to read refresh tokens from console logs. In updateSession, debug logging passes session.refreshToken and the newly returned refreshToken directly to console.log during token renewal. The disabled-by-default debug flag must be enabled and a session refresh must occur; access to the resulting logs exposes reusable authentication material.
The record
- CVE
- CVE-2024-51752
- Published
- Nov 5, 2024
- Updated
- Nov 5, 2024
- Vendor
- WorkOS
- Product
- AuthKit Next.js
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 5, 2024CVE publishedPublication date reported by the CVE source.
- Nov 5, 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=< 0.13.2
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