CVE-2017-2643: Infoleak
Published Mar 26, 2017
·Updated
In Moodle 3.2.x, global search displays user names for unauthenticated users.
Affected Software
9 affected componentsFixes available
composer/moodle/moodle>=3.2<3.2.2
3.2.2
Moodle moodle=3.2.0
Moodle moodle=3.2.0-beta
Moodle moodle=3.2.0-rc1
Moodle moodle=3.2.0-rc2
Moodle moodle=3.2.0-rc3
Moodle moodle=3.2.0-rc4
Moodle moodle=3.2.0-rc5
Moodle moodle=3.2.1
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/moodle/moodleto a version that resolves this vulnerability.Fixed in 3.2.2
Event History
Mar 26, 2017
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
DescriptionWeakness
Data Sourced
via NVD·06:59 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 17, 2022
Advisory Published
via GitHub·02:30 AM
Frequently Asked Questions
1
What is the severity of CVE-2017-2643?
CVE-2017-2643 is classified as a medium severity vulnerability.
2
How do I fix CVE-2017-2643?
To fix CVE-2017-2643, upgrade Moodle to version 3.2.2 or later.
3
What is the impact of CVE-2017-2643?
CVE-2017-2643 allows unauthenticated users to view usernames, potentially compromising user privacy.
4
Which versions of Moodle are affected by CVE-2017-2643?
Moodle versions 3.2.0, 3.2.0-beta, and 3.2.1 are affected by CVE-2017-2643.
5
Is there a workaround for CVE-2017-2643?
There is no official workaround for CVE-2017-2643; the recommended mitigation is to update to a secure version.