fkie_cve-2024-53858
Vulnerability from fkie_nvd
Published
2024-11-27 22:15
Modified
2024-11-27 22:15
Severity ?
6.5 (Medium) - CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L
Summary
The gh cli is GitHub’s official command line tool. A security vulnerability has been identified in the GitHub CLI that could leak authentication tokens when cloning repositories containing `git` submodules hosted outside of GitHub.com and ghe.com. This vulnerability stems from several `gh` commands used to clone a repository with submodules from a non-GitHub host including `gh repo clone`, `gh repo fork`, and `gh pr checkout`. These GitHub CLI commands invoke git with instructions to retrieve authentication tokens using the `credential.helper` configuration variable for any host encountered. Prior to version `2.63.0`, hosts other than GitHub.com and ghe.com are treated as GitHub Enterprise Server hosts and have tokens sourced from the following environment variables before falling back to host-specific tokens stored within system-specific secured storage: 1. `GITHUB_ENTERPRISE_TOKEN`, 2. `GH_ENTERPRISE_TOKEN` and 3. `GITHUB_TOKEN` when the `CODESPACES` environment variable is set. The result being `git` sending authentication tokens when cloning submodules. In version `2.63.0`, these GitHub CLI commands will limit the hosts for which `gh` acts as a credential helper to source authentication tokens. Additionally, `GITHUB_TOKEN` will only be used for GitHub.com and ghe.com. Users are advised to upgrade. Additionally users are advised to revoke authentication tokens used with the GitHub CLI and to review their personal security log and any relevant audit logs for actions associated with their account or enterprise
References
security-advisories@github.comhttps://git-scm.com/docs/gitcredentials
security-advisories@github.comhttps://github.com/cli/cli/security/advisories/GHSA-jwcm-9g39-pmcw
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "The gh cli is GitHub’s official command line tool. A security vulnerability has been identified in the GitHub CLI that could leak authentication tokens when cloning repositories containing `git` submodules hosted outside of GitHub.com and ghe.com. This vulnerability stems from several `gh` commands used to clone a repository with submodules from a non-GitHub host including `gh repo clone`, `gh repo fork`, and `gh pr checkout`. These GitHub CLI commands invoke git with instructions to retrieve authentication tokens using the `credential.helper` configuration variable for any host encountered. Prior to version `2.63.0`, hosts other than GitHub.com and ghe.com are treated as GitHub Enterprise Server hosts and have tokens sourced from the following environment variables before falling back to host-specific tokens stored within system-specific secured storage: 1. `GITHUB_ENTERPRISE_TOKEN`, 2. `GH_ENTERPRISE_TOKEN` and 3. `GITHUB_TOKEN` when the `CODESPACES` environment variable is set. The result being `git` sending authentication tokens when cloning submodules. In version `2.63.0`, these GitHub CLI commands will limit the hosts for which `gh` acts as a credential helper to source authentication tokens. Additionally, `GITHUB_TOKEN` will only be used for GitHub.com and ghe.com. Users are advised to upgrade. Additionally users are advised to revoke authentication tokens used with the GitHub CLI and to review their personal security log and any relevant audit logs for actions associated with their account or enterprise",
      },
      {
         lang: "es",
         value: "La CLI de gh es la herramienta de línea de comandos oficial de GitHub. Se ha identificado una vulnerabilidad de seguridad en la CLI de GitHub que podría filtrar tokens de autenticación al clonar repositorios que contienen submódulos `git` alojados fuera de GitHub.com y ghe.com. Esta vulnerabilidad se origina en varios comandos `gh` utilizados para clonar un repositorio con submódulos de un host que no es de GitHub, incluidos `gh repo clone`, `gh repo fork` y `gh pr checkout`. Estos comandos de la CLI de GitHub invocan git con instrucciones para recuperar tokens de autenticación utilizando la variable de configuración `credential.helper` para cualquier host encontrado. Antes de la versión `2.63.0`, los hosts que no sean GitHub.com y ghe.com se tratan como hosts de GitHub Enterprise Server y tienen tokens provenientes de las siguientes variables de entorno antes de recurrir a tokens específicos del host almacenados dentro de un almacenamiento seguro específico del sistema: 1. `GITHUB_ENTERPRISE_TOKEN`, 2. `GH_ENTERPRISE_TOKEN` y 3. `GITHUB_TOKEN` cuando se establece la variable de entorno `CODESPACES`. El resultado es que `git` envía tokens de autenticación al clonar submódulos. En la versión `2.63.0`, estos comandos de la CLI de GitHub limitarán los hosts para los que `gh` actúa como un asistente de credenciales para obtener tokens de autenticación. Además, `GITHUB_TOKEN` solo se usará para GitHub.com y ghe.com. Se recomienda a los usuarios que actualicen. Además, se recomienda a los usuarios revocar los tokens de autenticación utilizados con la CLI de GitHub y revisar su registro de seguridad personal y cualquier registro de auditoría relevante para las acciones asociadas con su cuenta o empresa.",
      },
   ],
   id: "CVE-2024-53858",
   lastModified: "2024-11-27T22:15:05.520",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "HIGH",
               attackVector: "LOCAL",
               availabilityImpact: "LOW",
               baseScore: 6.5,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "HIGH",
               integrityImpact: "HIGH",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "REQUIRED",
               vectorString: "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L",
               version: "3.1",
            },
            exploitabilityScore: 1,
            impactScore: 5.5,
            source: "security-advisories@github.com",
            type: "Secondary",
         },
      ],
   },
   published: "2024-11-27T22:15:05.520",
   references: [
      {
         source: "security-advisories@github.com",
         url: "https://git-scm.com/docs/gitcredentials",
      },
      {
         source: "security-advisories@github.com",
         url: "https://github.com/cli/cli/security/advisories/GHSA-jwcm-9g39-pmcw",
      },
   ],
   sourceIdentifier: "security-advisories@github.com",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-200",
            },
         ],
         source: "security-advisories@github.com",
         type: "Secondary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




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.