CVE-2023-51663 Hail authentication can be bypassed by changing email address
Attackers can bypass domain-based authentication by changing their email address, gaining unauthorized access to run jobs or create tenants in Hail Batch clusters.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-51663?
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.
Official 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.
Weakness: CWE-289
Which versions are affected by CVE-2023-51663?
3 open source packages ship an affected version, including hail. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
hail PyPI | All versions | 0.2.127 |
hail PyPI | All versions | 0.2.127 |
hail PyPI | All versions | 0.2.127 |
Products include Hail Hail.
How do I fix CVE-2023-51663?
Upgrade hail to 0.2.127 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2023-51663 being exploited?
There is no known exploitation of CVE-2023-51663 in the wild and no public exploit code.
Sources
Also known as GHSA-487p-qx68-5vjw, PYSEC-2023-271.