GHSA-fm5h-58g2-4m3f BIT-moodle-2023-5549 CVE-2023-5549
Moodle Improper Access Control vulnerability
- Severity
- 5.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.59%
- Chance of exploitation in the next 30 days. Higher than 48.31% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
4.3.0-rc2- Upgrade moodle/moodle to this version or later
Description
Insufficient web service capability checks made it possible to move categories a user had permission to manage, to a parent category they did not have the capability to manage.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| moodle/moodle | < 4.3.0-rc2 |
4.3.0-rc2 |
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 → 4.3.0-rc2
- composer
composer require moodle/moodle:^4.3.0-rc2
Severity breakdown
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Weakness
CWE-269: Improper Privilege Management
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
How to prevent it
- Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design: Follow the principle of least privilege when assigning access rights to entities in a software system.
- Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
CWE-284: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How to prevent it
- Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
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