cve-2023-51663
Vulnerability from cvelistv5
Published
2023-12-29 16:53
Modified
2024-08-02 22:40
Summary
Hail authentication can be bypassed by changing email address
Impacted products
hail-ishail
Show details on NVD website


{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T22:40:34.155Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "name": "https://github.com/hail-is/hail/security/advisories/GHSA-487p-qx68-5vjw",
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://github.com/hail-is/hail/security/advisories/GHSA-487p-qx68-5vjw"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "hail",
          "vendor": "hail-is",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 0.2.127"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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\u0027s 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."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "LOW",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "NONE",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-289",
              "description": "CWE-289: Authentication Bypass by Alternate Name",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2023-12-29T16:53:36.692Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/hail-is/hail/security/advisories/GHSA-487p-qx68-5vjw",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/hail-is/hail/security/advisories/GHSA-487p-qx68-5vjw"
        }
      ],
      "source": {
        "advisory": "GHSA-487p-qx68-5vjw",
        "discovery": "UNKNOWN"
      },
      "title": "Hail authentication can be bypassed by changing email address"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2023-51663",
    "datePublished": "2023-12-29T16:53:36.692Z",
    "dateReserved": "2023-12-21T14:14:26.224Z",
    "dateUpdated": "2024-08-02T22:40:34.155Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2023-51663\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2023-12-29T17:16:07.363\",\"lastModified\":\"2024-01-05T23:36:20.463\",\"vulnStatus\":\"Analyzed\",\"descriptions\":[{\"lang\":\"en\",\"value\":\"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\u0027s 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.\"},{\"lang\":\"es\",\"value\":\"Hail es una herramienta de an\u00e1lisis de datos de c\u00f3digo abierto, de uso general y basada en Python con tipos de datos y m\u00e9todos adicionales para trabajar con datos gen\u00f3micos. Hail depende de las direcciones de correo electr\u00f3nico de OpenID Connect (OIDC) de los tokens de identificaci\u00f3n para verificar la validez del dominio de un usuario, pero debido a que los usuarios tienen la capacidad de cambiar su direcci\u00f3n de correo electr\u00f3nico, podr\u00edan crear cuentas y usar recursos en cl\u00fasteres a los que no deber\u00edan tener acceso. Por ejemplo, un usuario podr\u00eda crear una cuenta de Microsoft o Google y luego cambiar su correo electr\u00f3nico a `test@example.org`. Luego, esta cuenta se puede usar para crear una cuenta de Hail Batch en cl\u00fasteres de Hail Batch cuyo dominio de organizaci\u00f3n es `example.org`. El atacante no puede acceder a datos privados ni hacerse pasar por otro usuario, pero tendr\u00eda la capacidad de ejecutar trabajos si los proyectos de facturaci\u00f3n Hail Batch est\u00e1n habilitados y crear Azure Tenants si tienen acceso a Azure Active Directory Administrator.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"LOW\",\"availabilityImpact\":\"NONE\",\"baseScore\":5.3,\"baseSeverity\":\"MEDIUM\"},\"exploitabilityScore\":3.9,\"impactScore\":1.4},{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"LOW\",\"baseScore\":5.3,\"baseSeverity\":\"MEDIUM\"},\"exploitabilityScore\":3.9,\"impactScore\":1.4}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-289\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:hail:hail:*:*:*:*:*:python:*:*\",\"versionEndExcluding\":\"0.2.127\",\"matchCriteriaId\":\"93EC3CA1-BC31-491A-A1F0-5D23431D34FA\"}]}]}],\"references\":[{\"url\":\"https://github.com/hail-is/hail/security/advisories/GHSA-487p-qx68-5vjw\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Mitigation\",\"Third Party Advisory\"]}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading...

Loading...

Loading...

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.