Skip to content

GHSA-9r26-5w88-qhp9 BIT-moodle-2024-25983 CVE-2024-25983

Authorization Bypass in moodle

Medium Packagist
Severity
5.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.60%
Chance of exploitation in the next 30 days. Higher than 48.82% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Fix
4.3.3
Upgrade moodle/moodle to this version or later

Description

Insufficient checks in a web service made it possible to add comments to the comments block on another user's dashboard when it was not otherwise available (e.g., on their profile page).

Affected versions

Packagist

PackageVulnerableFixed in
moodle/moodle
>= 4.3.0, < 4.3.3
4.3.3
moodle/moodle
>= 4.2.0, < 4.2.6
4.2.6
moodle/moodle
< 4.1.9
4.1.9

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.3

composer
composer require moodle/moodle:^4.3.3

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-639: Authorization Bypass Through User-Controlled Key

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

How to prevent it
  • Architecture and Design: For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
  • Architecture and Design, Implementation: Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
  • Architecture and Design: Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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
Is this in your code?

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