{"answers":{"affected":"2 open source packages ship an affected version, including omniauth-apple. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26254 in the wild and no public exploit code.","fix":"Upgrade omniauth-apple to 1.0.1 or later.","what":"CVE-2020-26254 is a high-severity authentication bypass vulnerability in nhosoya omniauth-apple, published on 8 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-26254 and fix it if it is affected.\n\nWhat it is: CVE-2020-26254 is a high-severity authentication bypass vulnerability in nhosoya omniauth-apple, published on 8 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-26254 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- omniauth-apple (RubyGems): affected all versions; fixed in 1.0.1\n- omniauth-apple (RubyGems): affected all versions; fixed in 1.0.1\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-2020-26254/ (Markdown: https://insights.sbomify.com/CVE-2020-26254/index.md)","id":"CVE-2020-26254","markdown":"https://insights.sbomify.com/CVE-2020-26254/index.md","name":"CVE-2020-26254","record":{"aliases":["GHSA-49r3-2549-3633"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby authentication gem","requires_auth":"low_privilege","summary":"Attackers can spoof email addresses during Apple Sign-In, potentially leading to account takeover in applications relying on email for identification.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"omniauth-apple","vendor":"omniauth-apple_project"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"omniauth-apple is the OmniAuth strategy for \"Sign In with Apple\" (RubyGem omniauth-apple). In omniauth-apple before version 1.0.1 attackers can fake their email address during authentication. This vulnerability impacts applications using the omniauth-apple strategy of OmniAuth and using the info.email field of OmniAuth's Auth Hash Schema for any kind of identification. The value of this field may be set to any value of the attacker's choice including email addresses of other users. Applications not using info.email for identification but are instead using the uid field are not impacted in the same manner. Note, these applications may still be negatively affected if the value of info.email is being used for other purposes. Applications using affected versions of omniauth-apple are advised to upgrade to omniauth-apple version 1.0.1 or later.","ecosystems":["RubyGems"],"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":"omniauth-apple allows attacker to fake their email address during authentication","id":"CVE-2020-26254","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":2,"n_references":3,"next":{"headline":"PHP Phar archives could be uploaded and executed in Kirby","id":"CVE-2020-26255"},"packages":[{"ecosystem":"RubyGems","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"omniauth-apple","purl":null,"source":"GHSA-49r3-2549-3633"},{"ecosystem":"RubyGems","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"omniauth-apple","purl":"pkg:gem/omniauth-apple","source":"GHSA-49r3-2549-3633"}],"prev":{"headline":".dev domains treated as local in Kirby","id":"CVE-2020-26253"},"products":["omniauth-apple"],"published":"2020-12-08","related":[],"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":"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["nhosoya"]},"summary":"Attackers can spoof email addresses during Apple Sign-In, potentially leading to account takeover in applications relying on email for identification.","url":"https://insights.sbomify.com/CVE-2020-26254/"}