CVE-2021-41242
Summary
| CVE | CVE-2021-41242 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2021-12-10 23:15:00 UTC |
| Updated | 2022-08-09 13:18:00 UTC |
| Description | OpenOlat is a web-basedlearning management system. A path traversal vulnerability exists in OpenOlat prior to versions 15.5.12 and 16.0.5. By providing a filename that contains a relative path as a parameter in some REST methods, it is possible to create directory structures and write files anywhere on the target system. The attack could be used to write files anywhere in the web root folder or outside, depending on the configuration of the system and the properly configured permission of the application server user. The attack requires an OpenOlat user account, an enabled REST API and the rights on a business object to call the vulnerable REST calls. The problem is fixed in version 15.5.12 and 16.0.5. There is a workaround available. The vulnerability requires the REST module to be enabled. Disabling the REST module or limiting the REST module via some firewall or web-server access rules to be accessed only be trusted systems will mitigate the risk. |
Risk And Classification
Problem Types: CWE-22
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Log in - OpenOlat Issue Management | MISC | jira.openolat.org | |
| OO-5819: container can only create file in its own path · OpenOLAT/OpenOLAT@c450df7 · GitHub | MISC | github.com | |
| OO-5819: clean starting / for backward compatibility · OpenOLAT/OpenOLAT@336d5ce · GitHub | MISC | github.com | |
| Path Traversal in some REST methods leading to file upload to arbitrary places · Advisory · OpenOLAT/OpenOLAT · GitHub | CONFIRM | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.