GHSA-358r-g2xw-7c83 CVE-2012-1156
Moodle backs up private files
High
Packagist
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 2.14%
- Chance of exploitation in the next 30 days. Higher than 82.05% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-532 Insertion of Sensitive Information into Log File
- Fix
2.2.2- Upgrade moodle/moodle to this version or later
Description
Moodle before 2.2.2, 2.1.5, and 2.0.8 had users' private files included in course backups unnecessarily.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| moodle/moodle | >= 2.2, < 2.2.2 |
2.2.2 |
| moodle/moodle | >= 2.1, < 2.1.5 |
2.1.5 |
| moodle/moodle | >= 2.0, < 2.0.8 |
2.0.8 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
moodle/moodle Packagist → 2.2.2
- composer
composer require moodle/moodle:^2.2.2
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-532: Insertion of Sensitive Information into Log File
The product writes sensitive information to a log file.
How to prevent it
- Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
- Distribution: Remove debug log files before deploying the application into production.
- Operation: Protect log files against unauthorized read/write.
- Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.
References
Advisories
Packages
Other links
- github.com/moodle/moodle/commit/37b6e7a03c77ea99fbe5224a15419e318019c570
- github.com/moodle/moodle/commit/ac6dc09c261219afa0191e9f2daf030bd071d272
- github.com/moodle/moodle/commit/f88224624dca76e1a8a2810fd8cc04292611f91c
- access.redhat.com/security/cve/cve-2012-1156
- bugzilla.redhat.com/show_bug.cgi
- moodle.org/mod/forum/discuss.php
- security-tracker.debian.org/tracker/CVE-2012-1156
- docs.moodle.org/dev/Moodle_2.0.8_release_notes
- docs.moodle.org/dev/Moodle_2.1.5_release_notes
- docs.moodle.org/dev/Moodle_2.2.2_release_notes
- lists.fedoraproject.org/pipermail/package-announce/2012-April/077635.html
- lists.fedoraproject.org/pipermail/package-announce/2012-April/078209.html
- lists.fedoraproject.org/pipermail/package-announce/2012-April/078210.html
- lists.fedoraproject.org/pipermail/package-announce/2012-May/080712.html
- lists.fedoraproject.org/pipermail/package-announce/2012-May/081047.html
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-cg8j-5cr2-568q Moodle TeX formula editor is vulnerable to DoS through lack of execution time limits | Medium | Also affects moodle/moodle |
| GHSA-ggxq-2mg9-8966 Moodle has a Remote Code Execution risk via file restore | High | Also affects moodle/moodle |
| GHSA-8jrv-wx83-w3xj Moodle Inserts Sensitive Information Into Sent Data | Medium | Also affects moodle/moodle |
| GHSA-hcm6-q6pc-xfhm Moodle has an authorization logic flaw | Critical | Also affects moodle/moodle |
| GHSA-vwhw-vp9v-q9c9 Moodle vulnerable to Cross-site Scripting | Medium | Also affects moodle/moodle |
| GHSA-5cx4-w4fh-fr57 Moodle Affected by Improper Restriction of Excessive Authentication Attempts | High | Also affects moodle/moodle |
| GHSA-qv78-6gpp-hm68 Moodle Open Redirect vulnerability | Medium | Also affects moodle/moodle |
| GHSA-qfh6-h7j6-fvjv Moodle formula injection vulnerability | High | Also affects moodle/moodle |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor