Token theft via unprotected approval requests
Published Oct 6, 2022 · Updated Apr 22, 2025
Missing authorization in Dex before 2.35.0 allows remote attackers to steal an OAuth code and obtain a token through a victim's OIDC login. The approval handler accepts a predictable request ID without authenticating it, letting an attacker poll the approval endpoint first and claim the completed flow. Exploitation requires a public client and victim interaction; the resulting token grants access to applications that trust the affected Dex instance.
Summary
What happened
Missing authorization in Dex before 2.35.0 allows remote attackers to steal an OAuth code and obtain a token through a victim's OIDC login. The approval handler accepts a predictable request ID without authenticating it, letting an attacker poll the approval endpoint first and claim the completed flow. Exploitation requires a public client and victim interaction; the resulting token grants access to applications that trust the affected Dex instance.
The record
- CVE
- CVE-2022-39222
- Published
- Oct 6, 2022
- Updated
- Apr 22, 2025
- Vendor
- Dex
- Product
- Dex
- Classifications
- CWE-862, CWE-200, T1528
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 6, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record 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=< 2.35.0
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
- Upstream approval-race reproduction procedurefunctional · demonstrated
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