Quick answers
- Is CVE-2016-5012 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2016-5012 being exploited in the wild.
- How severe is CVE-2016-5012?
- Medium severity, with a CVSS score of 5.3, published 20 January 2017.
- Which products and versions are affected?
- Moodle 3.1.0, 3.1.0 beta, 3.1.0 rc1, 3.1.0 rc2; moodle/moodle (Packagist) ECOSYSTEM:introduced=3.1,fixed=3.1.1.
- Is there a fix for CVE-2016-5012?
- Yes. moodle/moodle (Packagist): upgrade to 3.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2016-5012 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2016-5012?
- Check whether you run Moodle or moodle/moodle (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- moodle/moodle (Packagist): upgrade to 3.1.1 or later
composer require moodle/moodle:^3.1.1
Technical details
An information disclosure vulnerability (CWE-200) exists in Moodle 3.1.x. The root cause is a failure in the glossary search component to perform adequate authorization checks before displaying search results. A remote, unauthenticated attacker can exploit this by performing a search, which may return and display glossary entries that the user does not have the required permissions to view. This allows for the bypass of intended access controls on glossary content. A patch has been released by the vendor to address this permission check failure.
Affected products
- Moodle Moodle 3.1.0, 3.1.0 beta, 3.1.0 rc1, 3.1.0 rc2
Identifiers
- CVE-2016-5012
- GHSA-g58x-p3pj-rg52
Timeline
- 2016-07-18: disclosed: Initial disclosure via SecurityFocus and Moodle forums
- 2017-01-20: advisory: NVD publication date
- 2016-07-18: patched: Vendor advisory and patch released