Unauthorized actions via CSRF token timing leak
Published Aug 16, 2023 · Updated Oct 3, 2024
Timing-based CSRF token exposure in Oppia before 3.3.2-hotfix-2 allows remote attackers to perform a logged-in user's authorized actions. CsrfTokenManager.is_csrf_token_valid uses ordinary string equality, leaking token-prefix information through response timing instead of comparing in constant time. Exploitation requires a logged-in user to visit an attacker-controlled site and completion within one second; account credentials remain unaffected.
Summary
What happened
Timing-based CSRF token exposure in Oppia before 3.3.2-hotfix-2 allows remote attackers to perform a logged-in user's authorized actions. CsrfTokenManager.is_csrf_token_valid uses ordinary string equality, leaking token-prefix information through response timing instead of comparing in constant time. Exploitation requires a logged-in user to visit an attacker-controlled site and completion within one second; account credentials remain unaffected.
The record
- CVE
- CVE-2023-40021
- Published
- Aug 16, 2023
- Updated
- Oct 3, 2024
- Vendor
- Oppia Foundation
- Product
- Oppia
- Classifications
- CWE-203, CWE-208, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 16, 2023CVE publishedPublication date reported by the CVE source.
- Oct 3, 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=1.1.0 <3.3.2
- Affected versionversion=>= 1.1.0, < 3.3.2-hotfix-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
- GitHub Security Advisory attack exampleproof of concept · 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