{"answers":{"affected":"3 open source packages ship an affected version, including hail. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-51663 in the wild and no public exploit code.","fix":"Upgrade hail to 0.2.127 or later.","what":"CVE-2023-51663 is a medium-severity authentication bypass vulnerability in hail-is hail, published on 29 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-51663 and fix it if it is affected.\n\nWhat it is: CVE-2023-51663 is a medium-severity authentication bypass vulnerability in hail-is hail, published on 29 Dec 2023. 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-2023-51663 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hail (PyPI): affected all versions; fixed in 0.2.127\n- hail (PyPI): affected all versions; fixed in 0.2.127\n- hail (PyPI): affected all versions; fixed in 0.2.127\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-2023-51663/ (Markdown: https://insights.sbomify.com/CVE-2023-51663/index.md)","id":"CVE-2023-51663","markdown":"https://insights.sbomify.com/CVE-2023-51663/index.md","name":"CVE-2023-51663","record":{"aliases":["GHSA-487p-qx68-5vjw","PYSEC-2023-271"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["privilege_escalation","other"],"network_reachable":"yes","non_default_config":true,"product_category":"Hail genomic data tool","requires_auth":"none","summary":"Attackers can bypass domain-based authentication by changing their email address, gaining unauthorized access to run jobs or create tenants in Hail Batch clusters.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hail","vendor":"hail"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-289","name":"Authentication Bypass by Alternate Name"}],"description":"Hail is an open-source, general-purpose, Python-based data analysis tool with additional data types and methods for working with genomic data. Hail relies on OpenID Connect (OIDC) email addresses from ID tokens to verify the validity of a user's domain, but because users have the ability to change their email address, they could create accounts and use resources in clusters that they should not have access to. For example, a user could create a Microsoft or Google account and then change their email to `test@example.org`. This account can then be used to create a Hail Batch account in Hail Batch clusters whose organization domain is `example.org`. The attacker is not able to access private data or impersonate another user, but they would have the ability to run jobs if Hail Batch billing projects are enabled and create Azure Tenants if they have Azure Active Directory Administrator access.","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":"Hail authentication can be bypassed by changing email address","id":"CVE-2023-51663","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2023"},"n_packages":3,"n_references":1,"next":{"headline":"tj-actions/changed-files command injection in output filenames","id":"CVE-2023-51664"},"packages":[{"ecosystem":"PyPI","fixed":["0.2.127"],"introduced":["0"],"last_affected":[],"package":"hail","purl":null,"source":"GHSA-487p-qx68-5vjw"},{"ecosystem":"PyPI","fixed":["0.2.127"],"introduced":["0"],"last_affected":[],"package":"hail","purl":"pkg:pypi/hail","source":"GHSA-487p-qx68-5vjw"},{"ecosystem":"PyPI","fixed":["0.2.127"],"introduced":["0"],"last_affected":[],"package":"hail","purl":"pkg:pypi/hail","source":"PYSEC-2023-271"}],"prev":{"headline":"Snowflake Connector .NET does not properly check the Certificate Revocation List (CRL)","id":"CVE-2023-51662"},"products":["hail"],"published":"2023-12-29","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":"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":"total"},"state":"PUBLISHED","updated":"2025-04-17","vendors":["hail-is"]},"summary":"Attackers can bypass domain-based authentication by changing their email address, gaining unauthorized access to run jobs or create tenants in Hail Batch clusters.","url":"https://insights.sbomify.com/CVE-2023-51663/"}