Token disclosure via non-constant-time comparison
Published Apr 23, 2021 · Updated Sep 16, 2024
Timing discrepancy in Vaadin 7.0.0 through 7.7.23 and 8.0.0 through 8.12.2 allows attackers to infer tokens from UIDL requests. The UIDL handler compares supplied CSRF tokens without constant-time semantics, so invalid-request rejection latency varies with token content. Exploitation requires repeated timing measurements; a recovered token permits blind data submission as the user or listening to WebSocket-published data.
Summary
What happened
Timing discrepancy in Vaadin 7.0.0 through 7.7.23 and 8.0.0 through 8.12.2 allows attackers to infer tokens from UIDL requests. The UIDL handler compares supplied CSRF tokens without constant-time semantics, so invalid-request rejection latency varies with token content. Exploitation requires repeated timing measurements; a recovered token permits blind data submission as the user or listening to WebSocket-published data.
The record
- CVE
- CVE-2021-31403
- Published
- Apr 23, 2021
- Updated
- Sep 16, 2024
- Vendor
- Vaadin
- Product
- Vaadin Framework
- Classifications
- CWE-203, CWE-208
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 23, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=7.0.0 <* changes=[{"at":"8.0.0","status":"affected"}]
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.
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