{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36073 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36073 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36073 is a high-severity vulnerability in rubygems.org, published on 7 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36073 and fix it if it is affected.\n\nWhat it is: CVE-2022-36073 is a high-severity vulnerability in rubygems.org, published on 7 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-36073 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-2022-36073/ (Markdown: https://insights.sbomify.com/CVE-2022-36073/index.md)","id":"CVE-2022-36073","markdown":"https://insights.sbomify.com/CVE-2022-36073/index.md","name":"CVE-2022-36073","record":{"aliases":["GHSA-8qpf-wf2p-25vg"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"RubyGems.org","requires_auth":"low_privilege","summary":"Attackers can change account emails to unowned addresses, enabling future account takeover and malicious gem publishing when legitimate users reset passwords.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rubygems","vendor":"rubygems"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"RubyGems.org is the Ruby community gem host. A bug in password \u0026 email change confirmation code allowed an attacker to change their RubyGems.org account's email to an unowned email address. Having access to an account whose email has been changed could enable an attacker to save API keys for that account, and when a legitimate user attempts to create an account with their email (and has to reset password to gain access) and is granted access to other gems, the attacker would then be able to publish and yank versions of those gems. Commit number 90c9e6aac2d91518b479c51d48275c57de492d4d contains a patch for this issue.","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 allows creation of users with arbitrary unverified emails","id":"CVE-2022-36073","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Authentication headers exposed on by Nextcloud Server","id":"CVE-2022-36074"},"packages":[],"prev":{"headline":"SilverwareGames.io used == for hashing instead of ===","id":"CVE-2022-36072"},"products":["rubygems.org"],"published":"2022-09-07","related":[{"cvss_score":7.8,"headline":"RubyGems Deserialization of Untrusted Data vulnerability","id":"CVE-2018-1000074","kev_date_added":null,"published":"2018-03-13"},{"cvss_score":7.5,"headline":"RubyGems Link Following vulnerability","id":"CVE-2018-1000073","kev_date_added":null,"published":"2018-03-13"},{"cvss_score":7.4,"headline":"RubyGems Delete directory using symlink when decompressing tar","id":"CVE-2019-8320","kev_date_added":null,"published":"2019-06-06"},{"cvss_score":5.8,"headline":"RubyGems HTTPS to HTTP redirect","id":"CVE-2012-2125","kev_date_added":null,"published":"2013-10-01"},{"cvss_score":5.5,"headline":"RubyGems Path Traversal vulnerability","id":"CVE-2018-1000079","kev_date_added":null,"published":"2018-03-13"},{"cvss_score":4.3,"headline":"RubyGems does not verify SSL certificate","id":"CVE-2012-2126","kev_date_added":null,"published":"2013-10-01"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["rubygems"]},"summary":"Attackers can change account emails to unowned addresses, enabling future account takeover and malicious gem publishing when legitimate users reset passwords.","url":"https://insights.sbomify.com/CVE-2022-36073/"}