{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-21654 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-21654 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-21654 is a medium-severity authentication bypass vulnerability in rubygems.org, published on 12 Jan 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-21654 and fix it if it is affected.\n\nWhat it is: CVE-2024-21654 is a medium-severity authentication bypass vulnerability in rubygems.org, published on 12 Jan 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-21654 in the wild and no public exploit code.\n\nAffected product: rubygems.org. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-21654/ (Markdown: https://insights.sbomify.com/CVE-2024-21654/index.md)","id":"CVE-2024-21654","markdown":"https://insights.sbomify.com/CVE-2024-21654/index.md","name":"CVE-2024-21654","record":{"aliases":["GHSA-4v23-vj8h-7jp2"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby gem hosting service","requires_auth":"none","summary":"Attackers can bypass MFA via the password reset function to take over user accounts on the Rubygems.org hosting service.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rubygems.org","vendor":"rubygems"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"Rubygems.org is the Ruby community's gem hosting service. Rubygems.org users with MFA enabled would normally be protected from account takeover in the case of email account takeover. However, a workaround on the forgotten password form allows an attacker to bypass the MFA requirement and takeover the account. This vulnerability has been patched in commit 0b3272a.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"rubygems.org MFA Bypass through password reset function could allow account takeover","id":"CVE-2024-21654","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Insufficient control of custom field value sizes","id":"CVE-2024-21655"},"packages":[],"prev":{"headline":"vantage6 insecure SSH configuration for node and server containers","id":"CVE-2024-21653"},"products":["rubygems.org"],"published":"2024-01-12","related":[{"cvss_score":9.9,"headline":"Unauthorized gem takeover for some gems on rubygems.org","id":"CVE-2022-29176","kev_date_added":null,"published":"2022-05-05"},{"cvss_score":7.7,"headline":"Unauthorized takeover for new versions of some platform-specific gems","id":"CVE-2022-29218","kev_date_added":null,"published":"2022-05-12"},{"cvss_score":7.4,"headline":"Unauthorized gem replacement for full names ending in numbers on rubygems.org","id":"CVE-2023-40165","kev_date_added":null,"published":"2023-08-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2024-10-24","vendors":["rubygems"]},"summary":"Attackers can bypass MFA via the password reset function to take over user accounts on the Rubygems.org hosting service.","url":"https://insights.sbomify.com/CVE-2024-21654/"}