Access-token disclosure via nonconstant-time comparison
Published Oct 14, 2022 · Updated Apr 23, 2025
Timing discrepancy in GoCD 19.2.0 through 19.10.0 allows remote attackers to infer user API access tokens through repeated requests. The GoCD Server access-token validator compares supplied and stored token strings with an ordinary early-exit comparison instead of a constant-time algorithm. No authentication or user interaction is required, but successful disclosure requires many precisely timed API calls and yields access under the compromised token's privileges.
Summary
What happened
Timing discrepancy in GoCD 19.2.0 through 19.10.0 allows remote attackers to infer user API access tokens through repeated requests. The GoCD Server access-token validator compares supplied and stored token strings with an ordinary early-exit comparison instead of a constant-time algorithm. No authentication or user interaction is required, but successful disclosure requires many precisely timed API calls and yields access under the compromised token's privileges.
The record
- CVE
- CVE-2022-39308
- Published
- Oct 14, 2022
- Updated
- Apr 23, 2025
- Vendor
- Thoughtworks
- Product
- GoCD
- Classifications
- CWE-697, CWE-208, CWE-1254, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 14, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=>= 19.2.0, < 19.11.0
What conditions does exploitation require?
What is affected?
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