Bitnami package
moodle
pkg:bitnami/moodle
Vulnerabilities (241)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2024-43432 | Med | 5.3 | < 4.1.12 | 4.1.12 | Nov 11, 2024 | A flaw was found in moodle. The cURL wrapper in Moodle strips HTTPAUTH and USERPWD headers during emulated redirects, but retains other original request headers, so HTTP authorization header information could be unintentionally sent in requests to redirect URLs. | |
| CVE-2024-43430 | Med | 5.3 | >= 4.4.0, < 4.4.2 | 4.4.2 | Nov 11, 2024 | A flaw was found in moodle. External API access to Quiz can override contained insufficient access control. | |
| CVE-2024-43429 | Med | 5.3 | < 4.1.12 | 4.1.12 | Nov 11, 2024 | A flaw was found in moodle. Some hidden user profile fields are visible in gradebook reports, which could result in users without the "view hidden user fields" capability having access to the information. | |
| CVE-2024-43427 | Low | 3.7 | < 4.1.12 | 4.1.12 | Nov 11, 2024 | A flaw was found in moodle. When creating an export of site administration presets, some sensitive secrets and keys are not being excluded from the export, which could result in them unintentionally being leaked if the presets are shared with a third party. | |
| CVE-2024-43440 | Hig | 7.5 | < 4.1.12 | 4.1.12 | Nov 7, 2024 | A flaw was found in moodle. A local file may include risks when restoring block backups. | |
| CVE-2024-43438 | Hig | 7.5 | >= 4.1.0, < 4.1.12 | 4.1.12 | Nov 7, 2024 | A flaw was found in Feedback. Bulk messaging in the activity's non-respondents report did not verify message recipients belonging to the set of users returned by the report. | |
| CVE-2024-43436 | Hig | 7.2 | >= 4.1.0, < 4.1.12 | 4.1.12 | Nov 7, 2024 | A SQL injection risk flaw was found in the XMLDB editor tool available to site administrators. | |
| CVE-2024-43434 | Hig | 8.1 | < 4.1.12 | 4.1.12 | Nov 7, 2024 | The bulk message sending feature in Moodle's Feedback module's non-respondents report had an incorrect CSRF token check, leading to a CSRF vulnerability. | |
| CVE-2024-43431 | Hig | 7.5 | < 4.1.12 | 4.1.12 | Nov 7, 2024 | A vulnerability was found in Moodle. Insufficient capability checks made it possible to delete badges that a user does not have permission to access. | |
| CVE-2024-43428 | Hig | 7.7 | < 4.1.12 | 4.1.12 | Nov 7, 2024 | To address a cache poisoning risk in Moodle, additional validation for local storage was required. | |
| CVE-2024-43426 | Hig | 7.5 | >= 4.1.0, < 4.1.12 | 4.1.12 | Nov 7, 2024 | A flaw was found in pdfTeX. Insufficient sanitizing in the TeX notation filter resulted in an arbitrary file read risk on sites where pdfTeX is available, such as those with TeX Live installed. | |
| CVE-2024-43425 | Hig | 8.1 | < 4.1.12 | 4.1.12 | Nov 7, 2024 | A flaw was found in Moodle. Additional restrictions are required to avoid a remote code execution risk in calculated question types. Note: This requires the capability to add/update questions. | |
| CVE-2024-37674 | Med | 5.5 | >= 3.10.0, < 4.1.10 | 4.1.10 | Jun 20, 2024 | Cross Site Scripting vulnerability in Moodle CMS v3.10 allows a remote attacker to execute arbitrary code via the Field Name (name parameter) of a new activity. | |
| CVE-2024-38277 | Med | 5.4 | >= 4.1.0, < 4.1.11 | 4.1.11 | Jun 18, 2024 | A unique key should be generated for a user's QR login key and their auto-login key, so the same key cannot be used interchangeably between the two. | |
| CVE-2024-38276 | Hig | 8.8 | < 4.1.10 | 4.1.10 | Jun 18, 2024 | Incorrect CSRF token checks resulted in multiple CSRF risks. | |
| CVE-2024-38275 | Hig | 7.5 | < 4.1.11 | 4.1.11 | Jun 18, 2024 | The cURL wrapper in Moodle retained the original request headers when following redirects, so HTTP authorization header information could be unintentionally sent in requests to redirect URLs. | |
| CVE-2024-38274 | Med | 6.1 | >= 4.1.0, < 4.1.11 | 4.1.11 | Jun 18, 2024 | Insufficient escaping of calendar event titles resulted in a stored XSS risk in the event deletion prompt. | |
| CVE-2024-38273 | Med | 5.4 | >= 4.1.0, < 4.1.11 | 4.1.11 | Jun 18, 2024 | Insufficient capability checks meant it was possible for users to gain access to BigBlueButton join URLs they did not have permission to access. | |
| CVE-2024-34009 | Hig | 7.5 | >= 4.3.0, < 4.3.4 | 4.3.4 | May 31, 2024 | Insufficient checks whether ReCAPTCHA was enabled made it possible to bypass the checks on the login page. This did not affect other pages where ReCAPTCHA is utilized. | |
| CVE-2024-34008 | Hig | 8.8 | >= 4.0.0, < 4.3.4 | 4.3.4 | May 31, 2024 | Actions in the admin management of analytics models did not include the necessary token to prevent a CSRF risk. |
- affected < 4.1.12fixed 4.1.12
A flaw was found in moodle. The cURL wrapper in Moodle strips HTTPAUTH and USERPWD headers during emulated redirects, but retains other original request headers, so HTTP authorization header information could be unintentionally sent in requests to redirect URLs.
- affected >= 4.4.0, < 4.4.2fixed 4.4.2
A flaw was found in moodle. External API access to Quiz can override contained insufficient access control.
- affected < 4.1.12fixed 4.1.12
A flaw was found in moodle. Some hidden user profile fields are visible in gradebook reports, which could result in users without the "view hidden user fields" capability having access to the information.
- affected < 4.1.12fixed 4.1.12
A flaw was found in moodle. When creating an export of site administration presets, some sensitive secrets and keys are not being excluded from the export, which could result in them unintentionally being leaked if the presets are shared with a third party.
- affected < 4.1.12fixed 4.1.12
A flaw was found in moodle. A local file may include risks when restoring block backups.
- affected >= 4.1.0, < 4.1.12fixed 4.1.12
A flaw was found in Feedback. Bulk messaging in the activity's non-respondents report did not verify message recipients belonging to the set of users returned by the report.
- affected >= 4.1.0, < 4.1.12fixed 4.1.12
A SQL injection risk flaw was found in the XMLDB editor tool available to site administrators.
- affected < 4.1.12fixed 4.1.12
The bulk message sending feature in Moodle's Feedback module's non-respondents report had an incorrect CSRF token check, leading to a CSRF vulnerability.
- affected < 4.1.12fixed 4.1.12
A vulnerability was found in Moodle. Insufficient capability checks made it possible to delete badges that a user does not have permission to access.
- affected < 4.1.12fixed 4.1.12
To address a cache poisoning risk in Moodle, additional validation for local storage was required.
- affected >= 4.1.0, < 4.1.12fixed 4.1.12
A flaw was found in pdfTeX. Insufficient sanitizing in the TeX notation filter resulted in an arbitrary file read risk on sites where pdfTeX is available, such as those with TeX Live installed.
- affected < 4.1.12fixed 4.1.12
A flaw was found in Moodle. Additional restrictions are required to avoid a remote code execution risk in calculated question types. Note: This requires the capability to add/update questions.
- affected >= 3.10.0, < 4.1.10fixed 4.1.10
Cross Site Scripting vulnerability in Moodle CMS v3.10 allows a remote attacker to execute arbitrary code via the Field Name (name parameter) of a new activity.
- affected >= 4.1.0, < 4.1.11fixed 4.1.11
A unique key should be generated for a user's QR login key and their auto-login key, so the same key cannot be used interchangeably between the two.
- affected < 4.1.10fixed 4.1.10
Incorrect CSRF token checks resulted in multiple CSRF risks.
- affected < 4.1.11fixed 4.1.11
The cURL wrapper in Moodle retained the original request headers when following redirects, so HTTP authorization header information could be unintentionally sent in requests to redirect URLs.
- affected >= 4.1.0, < 4.1.11fixed 4.1.11
Insufficient escaping of calendar event titles resulted in a stored XSS risk in the event deletion prompt.
- affected >= 4.1.0, < 4.1.11fixed 4.1.11
Insufficient capability checks meant it was possible for users to gain access to BigBlueButton join URLs they did not have permission to access.
- affected >= 4.3.0, < 4.3.4fixed 4.3.4
Insufficient checks whether ReCAPTCHA was enabled made it possible to bypass the checks on the login page. This did not affect other pages where ReCAPTCHA is utilized.
- affected >= 4.0.0, < 4.3.4fixed 4.3.4
Actions in the admin management of analytics models did not include the necessary token to prevent a CSRF risk.
Page 5 of 13