CVE-2024-24770: Username timing attack on recover password/MFA token in vantage6
Impact Much like https://github.com/vantage6/vantage6/security/advisories/GHSA-45gq-q4xh-cp53, it is possible to find which usernames exist in vantage6 by calling the API routes /recover/lost and /2fa/lost, which send emails to users if they have lost their password or MFA token. Usernames can be found by assessing response time differences, and additionally, they can be found because the endpoint gives a response "Failed to login" if the username exists.
Patches No
Workarounds No
Other sources
vantage6 is an open source framework built to enable, manage and deploy privacy enhancing technologies like Federated Learning and Multi-Party Computation. Much like GHSA-45gq-q4xh-cp53, it is possible to find which usernames exist in vantage6 by calling the API routes /recover/lost and /2fa/lost. These routes send emails to users if they have lost their password or MFA token. This issue has been addressed in commit aecfd6d0e and is expected to ship in subsequent releases. Users are advised to upgrade as soon as a new release is available. There are no known workarounds for this vulnerability.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-24770?
CVE-2024-24770 has been classified with a medium severity due to the potential for username enumeration via API endpoints.
How do I fix CVE-2024-24770?
To fix CVE-2024-24770, upgrade the vantage6 package to version 4.3.0 or later.
What vulnerability does CVE-2024-24770 exploit?
CVE-2024-24770 exploits the API routes that allow attackers to determine existing usernames through password recovery mechanisms.
Which versions of vantage6 are affected by CVE-2024-24770?
Versions of vantage6 from 4.2.2 and below are affected by CVE-2024-24770.
Is CVE-2024-24770 related to any similar vulnerabilities?
Yes, CVE-2024-24770 is related to similar vulnerabilities outlined in advisories for username enumeration issues.