{"answers":{"affected":"3 open source packages ship an affected version, including vantage6. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-24770 in the wild and no public exploit code.","fix":"Upgrade vantage6 to 4.3.0 or later.","what":"CVE-2024-24770 is a medium-severity vulnerability in vantage6, published on 14 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-24770 and fix it if it is affected.\n\nWhat it is: CVE-2024-24770 is a medium-severity vulnerability in vantage6, published on 14 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-24770 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vantage6 (PyPI): affected all versions; fixed in 4.3.0\n- vantage6 (PyPI): affected all versions; fixed in 4.3.0\n- vantage6 (PyPI): affected all versions; fixed in 4.3.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-24770/ (Markdown: https://insights.sbomify.com/CVE-2024-24770/index.md)","id":"CVE-2024-24770","markdown":"https://insights.sbomify.com/CVE-2024-24770/index.md","name":"CVE-2024-24770","record":{"aliases":["GHSA-5h3x-6gwf-73jm","PYSEC-2026-2005"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"vantage6 framework","requires_auth":"none","summary":"Attackers can enumerate valid usernames in vantage6 by observing timing differences in password and MFA recovery API responses.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vantage6","vendor":"vantage6"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"},{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Username timing attack on recover password/MFA token in vantage6","id":"CVE-2024-24770","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":3,"next":{"headline":"Open Forms potential multi-factor authentication bypass","id":"CVE-2024-24771"},"packages":[{"ecosystem":"PyPI","fixed":["4.3.0"],"introduced":["0"],"last_affected":[],"package":"vantage6","purl":null,"source":"GHSA-5h3x-6gwf-73jm"},{"ecosystem":"PyPI","fixed":["4.3.0"],"introduced":["0"],"last_affected":[],"package":"vantage6","purl":"pkg:pypi/vantage6","source":"GHSA-5h3x-6gwf-73jm"},{"ecosystem":"PyPI","fixed":["4.3.0"],"introduced":["0"],"last_affected":[],"package":"vantage6","purl":"pkg:pypi/vantage6","source":"PYSEC-2026-2005"}],"prev":{"headline":"Vantage6: No limit on emails sent for password/MFA reset","id":"CVE-2024-24769"},"products":["vantage6"],"published":"2024-03-14","related":[{"cvss_score":8.8,"headline":"Remote code execution","id":"CVE-2024-21649","kev_date_added":null,"published":"2024-01-30"},{"cvss_score":8.8,"headline":"Refresh tokens do not expire in Vantage6","id":"CVE-2023-23929","kev_date_added":null,"published":"2023-03-03"},{"cvss_score":7.2,"headline":"vantage6 Node accepts non-whitelisted algorithms from malicious server","id":"CVE-2023-47631","kev_date_added":null,"published":"2023-11-14"},{"cvss_score":6.5,"headline":"vantage6 insecure SSH configuration for node and server containers","id":"CVE-2024-21653","kev_date_added":null,"published":"2024-01-30"},{"cvss_score":6.3,"headline":"Improper Preservation of Permissions in vantage6","id":"CVE-2023-22738","kev_date_added":null,"published":"2023-03-01"},{"cvss_score":5.5,"headline":"vantage6's Pickle serialization is insecure","id":"CVE-2023-23930","kev_date_added":null,"published":"2023-10-11"},{"cvss_score":5.4,"headline":"Defining resource name as integer in vantage6 may give unintended access","id":"CVE-2023-28635","kev_date_added":null,"published":"2023-10-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-26","vendors":["vantage6"]},"summary":"Attackers can enumerate valid usernames in vantage6 by observing timing differences in password and MFA recovery API responses.","url":"https://insights.sbomify.com/CVE-2024-24770/"}