A flaw was found in moodle before versions 3.5.1, 3.4.4, 3.3.7. No option existed to omit logs from data privacy exports, which may contain details of other users who interacted with the requester.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Moodle | Moodle | 3.3.0 (including) | 3.3.7 (excluding) |
| Moodle | Moodle | 3.4.0 (including) | 3.4.4 (excluding) |
| Moodle | Moodle | 3.5.0 (including) | 3.5.1 (excluding) |
| Moodle | Ubuntu | artful | * |
| Moodle | Ubuntu | bionic | * |
| Moodle | Ubuntu | cosmic | * |
| Moodle | Ubuntu | disco | * |
| Moodle | Ubuntu | eoan | * |
| Moodle | Ubuntu | trusty | * |
| Moodle | Ubuntu | xenial | * |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: