Oppia 3.3.2
Approved changes feed: RSS · Atom
cpe:2.3:a:oppia:oppia:3.3.2:-:*:*:*:*:*:*part: a version: 3.3.2 update: -
| Vendor | Oppia (1857866d-f3b8-56a9-833a-a80c14ddc109) |
|---|---|
| Product | Oppia (0770c505-72bd-5fbd-b4be-414fb73b5ffd) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:bitbucket/kevinlee12/oppia |
purl2cpe | 2026-06-01 10:17:29.323804 |
pkg:github/oppia/oppia |
purl2cpe | 2026-06-01 10:17:29.323805 |
pkg:googlesource/oppia |
purl2cpe | 2026-06-01 10:17:29.323807 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-40021 |
vulnerable | 2026-06-08 06:09:41.038798 |
Timing Attack Reveals CSRF Tokens in oppia
MEDIUM (5.3)
Oppia is an online learning platform. When comparing a received CSRF token against the expected token, Oppia uses the string equality operator (`==`), which is not safe against timing attacks. By repeatedly submitting invalid tokens, an attacker can brute-force the expected CSRF token character by character. Once they have recovered the token, they can then submit a forged request on behalf of a logged-in user and execute privileged actions on that user's behalf. In particular the function to validate received CSRF tokens is at `oppia.core.controllers.base.CsrfTokenManager.is_csrf_token_valid`. An attacker who can lure a logged-in Oppia user to a malicious website can perform any change on Oppia that the user is authorized to do, including changing profile information; creating, deleting, and changing explorations; etc. Note that the attacker cannot change a user's login credentials. An attack would need to complete within 1 second because every second, the time used in computing the token changes. This issue has been addressed in commit `b89bf80837` which has been included in release `3.3.2-hotfix-2`. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Published: 2023-08-16T20:25:22.726Z
Updated: 2024-10-03T13:37:09.373Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.