CVE-2017-2642 Moodle User fullname disclosure on user preferences page
Medium 6.5
Published
Updated
Check this codebase for CVE-2017-2642 and fix it if it is affected.
What it is: CVE-2017-2642 is a medium-severity vulnerability in Moodle Moodle, published on 17 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-2642 in the wild and no public exploit code.
Affected packages and fixed versions:
- moodle/moodle (Packagist): affected from 3.1; fixed in 3.1.7
- moodle/moodle (Packagist): affected from 3.1; fixed in 3.1.7
- moodle/moodle (Packagist): affected from 3.2; fixed in 3.2.4
- moodle/moodle (Packagist): affected from 3.2; fixed in 3.2.4
- moodle/moodle (Packagist): affected from 3.3; fixed in 3.3.1
- moodle/moodle (Packagist): affected from 3.3; fixed in 3.3.1
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2017-2642/ (Markdown: https://insights.sbomify.com/CVE-2017-2642/index.md)
An attacker can view user full names on the preferences page, exposing personal data in Moodle installations.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2017-2642?
CVE-2017-2642 is a medium-severity vulnerability in Moodle Moodle, published on 17 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Moodle 3.x has user fullname disclosure on the user preferences page.
Weakness: CWE-200
Which versions are affected by CVE-2017-2642?
6 open source packages ship an affected version, including moodle/moodle. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
moodle/moodle Packagist | From 3.1 | 3.1.7 |
moodle/moodle Packagist | From 3.1 | 3.1.7 |
moodle/moodle Packagist | From 3.2 | 3.2.4 |
moodle/moodle Packagist | From 3.2 | 3.2.4 |
moodle/moodle Packagist | From 3.3 | 3.3.1 |
moodle/moodle Packagist | From 3.3 | 3.3.1 |
Products include Moodle Moodle.
How do I fix CVE-2017-2642?
Upgrade moodle/moodle to a fixed version for your release line: 3.1.7, 3.2.4 or 3.3.1.
Is CVE-2017-2642 being exploited?
There is no known exploitation of CVE-2017-2642 in the wild and no public exploit code.
Other vulnerabilities in Moodle Moodle
- CVE-2006-4935 File upload in n/a
- CVE-2006-4936 Moodle does not properly validate module instance id
- CVE-2004-2233 Unknown "front page vulnerability with Moodle servers" for Moodle before 1.3.2 has unknown impact and attack vectors.
- CVE-2004-2235 Cross-site scripting in n/a
- CVE-2004-2236 Other in n/a
Sources
Also known as GHSA-54r2-r67g-fr9m, UBUNTU-CVE-2017-2642.