CVE-2021-36539 json
Instructure Canvas LMS didn't properly deny access to locked/unpublished files when the unprivileged user access the DocViewer based file p…
published 3y ago modified 4mo ago also BIT-canvaslms-2021-36539 , EUVD-2021-23141
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
Instructure Canvas LMS didn't properly deny access to locked/unpublished files when the unprivileged user access the DocViewer based file preview URL (canvadoc_session_url).
Patch / fix
- bitnami canvaslms 2022-10-15.0.0
- instructure canvas_learning_management_service 2022-10-15
Is CVE-2021-36539 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.90% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/instructure/canvas-lms/issues/1905 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/gaukas/instructure-canvas-file-oracle referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | canvaslms | <2022-10-15.0.0 |
2022-10-15.0.0 |
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/instructure/canvas-lms/issues/1905
exploit, third-party-advisory, web
-
github.com
/gaukas/instructure-canvas-file-oracle
exploit, third-party-advisory, web
Sources
- CVE List CVE-2021-36539
- NVD CVE-2021-36539
- OSV BIT-canvaslms-2021-36539
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.