fkie_cve-2023-4759
Vulnerability from fkie_nvd
Published
2023-09-12 10:15
Modified
2024-11-21 08:35
Severity ?
8.8 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
8.8 (High) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
Arbitrary File Overwrite in Eclipse JGit <= 6.6.0 In Eclipse JGit, all versions <= 6.6.0.202305301015-r, a symbolic link present in a specially crafted git repository can be used to write a file to locations outside the working tree when this repository is cloned with JGit to a case-insensitive filesystem, or when a checkout from a clone of such a repository is performed on a case-insensitive filesystem. This can happen on checkout (DirCacheCheckout), merge (ResolveMerger via its WorkingTreeUpdater), pull (PullCommand using merge), and when applying a patch (PatchApplier). This can be exploited for remote code execution (RCE), for instance if the file written outside the working tree is a git filter that gets executed on a subsequent git command. The issue occurs only on case-insensitive filesystems, like the default filesystems on Windows and macOS. The user performing the clone or checkout must have the rights to create symbolic links for the problem to occur, and symbolic links must be enabled in the git configuration. Setting git configuration option core.symlinks = false before checking out avoids the problem. The issue was fixed in Eclipse JGit version 6.6.1.202309021850-r and 6.7.0.202309050840-r, available via Maven Central https://repo1.maven.org/maven2/org/eclipse/jgit/  and repo.eclipse.org https://repo.eclipse.org/content/repositories/jgit-releases/ . A backport is available in 5.13.3 starting from 5.13.3.202401111512-r. The JGit maintainers would like to thank RyotaK for finding and reporting this issue.
References
emo@eclipse.orghttps://git.eclipse.org/c/jgit/jgit.git/commit/?id=9072103f3b3cf64dd12ad2949836ab98f62dabf1Patch, Vendor Advisory
emo@eclipse.orghttps://gitlab.eclipse.org/security/vulnerability-reports/-/issues/11Issue Tracking, Vendor Advisory
emo@eclipse.orghttps://projects.eclipse.org/projects/technology.jgit/releases/6.6.1Release Notes, Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://git.eclipse.org/c/jgit/jgit.git/commit/?id=9072103f3b3cf64dd12ad2949836ab98f62dabf1Patch, Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/11Issue Tracking, Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://projects.eclipse.org/projects/technology.jgit/releases/6.6.1Release Notes, Vendor Advisory
Impacted products
Vendor Product Version
eclipse jgit *
eclipse jgit *
eclipse jgit *
apple macos -
microsoft windows -


To clipboard 

{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:a:eclipse:jgit:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "FD632A09-BA3F-40B4-9E87-1B3A1396B8D2",
                     versionEndExcluding: "5.13.3.202401111512-r",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:eclipse:jgit:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "E42260B6-CFAE-4C15-AD05-185450537107",
                     versionEndExcluding: "6.6.0.202305301015",
                     versionStartIncluding: "6.6.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:eclipse:jgit:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "A6A51C42-BDB6-4744-80CF-55291D1DC24F",
                     versionEndExcluding: "6.7.0.202309050840",
                     versionStartIncluding: "6.7.0",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:o:apple:macos:-:*:*:*:*:*:*:*",
                     matchCriteriaId: "387021A0-AF36-463C-A605-32EA7DAC172E",
                     vulnerable: false,
                  },
                  {
                     criteria: "cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*",
                     matchCriteriaId: "A2572D17-1DE6-457B-99CC-64AFD54487EA",
                     vulnerable: false,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
         operator: "AND",
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "Arbitrary File Overwrite in Eclipse JGit <= 6.6.0\n\nIn Eclipse JGit, all versions <= 6.6.0.202305301015-r, a symbolic link present in a specially crafted git repository can be used to write a file to locations outside the working tree when this repository is cloned with JGit to a case-insensitive filesystem, or when a checkout from a clone of such a repository is performed on a case-insensitive filesystem.\n\nThis can happen on checkout (DirCacheCheckout), merge (ResolveMerger via its WorkingTreeUpdater), pull (PullCommand using merge), and when applying a patch (PatchApplier). This can be exploited for remote code execution (RCE), for instance if the file written outside the working tree is a git filter that gets executed on a subsequent git command.\n\nThe issue occurs only on case-insensitive filesystems, like the default filesystems on Windows and macOS. The user performing the clone or checkout must have the rights to create symbolic links for the problem to occur, and symbolic links must be enabled in the git configuration.\n\nSetting git configuration option core.symlinks = false before checking out avoids the problem.\n\nThe issue was fixed in Eclipse JGit version 6.6.1.202309021850-r and 6.7.0.202309050840-r, available via  Maven Central https://repo1.maven.org/maven2/org/eclipse/jgit/  and  repo.eclipse.org https://repo.eclipse.org/content/repositories/jgit-releases/ . A backport is available in 5.13.3 starting from  5.13.3.202401111512-r.\n\n\nThe JGit maintainers would like to thank RyotaK for finding and reporting this issue.\n\n\n\n",
      },
      {
         lang: "es",
         value: "Sobrescritura Arbitraria de Archivos en Eclipse JGit &lt;= 6.6.0 En Eclipse JGit, todas las versiones &lt;= 6.6.0.202305301015-r, se puede utilizar un enlace simbólico presente en un repositorio git especialmente manipulado para escribir un archivo en ubicaciones fuera del árbol de trabajo cuando esto el repositorio se clona con JGit en un sistema de archivos que no distingue entre mayúsculas y minúsculas, o cuando se realiza una extracción de un clon de dicho repositorio en un sistema de archivos que no distingue entre mayúsculas y minúsculas. Esto puede suceder al finalizar la compra (DirCacheCheckout), fusionar (ResolveMerger a través de su WorkingTreeUpdater), extraer (PullCommand usando merge) y al aplicar un parche (PatchApplier). Esto se puede aprovechar para la ejecución remota de código (RCE), por ejemplo, si el archivo escrito fuera del árbol de trabajo es un filtro git que se ejecuta en un comando git posterior. El problema ocurre solo en sistemas de archivos que no distinguen entre mayúsculas y minúsculas, como los sistemas de archivos predeterminados en Windows y macOS. El usuario que realiza la clonación o el pago debe tener derechos para crear enlaces simbólicos para que ocurra el problema, y ??los enlaces simbólicos deben estar habilitados en la configuración de git. Configurar la opción de configuración de git core.symlinks = false antes de realizar el check-out evita el problema. El problema se solucionó en Eclipse JGit versión 6.6.1.202309021850-r y 6.7.0.202309050840-r, disponibles a través de Maven Central https://repo1.maven.org/maven2/org/eclipse/jgit/ y repo.eclipse.org https: //repo.eclipse.org/content/repositories/jgit-releases/. Los mantenedores de JGit desean agradecer a RyotaK por encontrar e informar este problema.",
      },
   ],
   id: "CVE-2023-4759",
   lastModified: "2024-11-21T08:35:55.110",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 8.8,
               baseSeverity: "HIGH",
               confidentialityImpact: "HIGH",
               integrityImpact: "HIGH",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "REQUIRED",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
               version: "3.1",
            },
            exploitabilityScore: 2.8,
            impactScore: 5.9,
            source: "emo@eclipse.org",
            type: "Secondary",
         },
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 8.8,
               baseSeverity: "HIGH",
               confidentialityImpact: "HIGH",
               integrityImpact: "HIGH",
               privilegesRequired: "LOW",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
               version: "3.1",
            },
            exploitabilityScore: 2.8,
            impactScore: 5.9,
            source: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2023-09-12T10:15:29.977",
   references: [
      {
         source: "emo@eclipse.org",
         tags: [
            "Patch",
            "Vendor Advisory",
         ],
         url: "https://git.eclipse.org/c/jgit/jgit.git/commit/?id=9072103f3b3cf64dd12ad2949836ab98f62dabf1",
      },
      {
         source: "emo@eclipse.org",
         tags: [
            "Issue Tracking",
            "Vendor Advisory",
         ],
         url: "https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/11",
      },
      {
         source: "emo@eclipse.org",
         tags: [
            "Release Notes",
            "Vendor Advisory",
         ],
         url: "https://projects.eclipse.org/projects/technology.jgit/releases/6.6.1",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Patch",
            "Vendor Advisory",
         ],
         url: "https://git.eclipse.org/c/jgit/jgit.git/commit/?id=9072103f3b3cf64dd12ad2949836ab98f62dabf1",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Issue Tracking",
            "Vendor Advisory",
         ],
         url: "https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/11",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Release Notes",
            "Vendor Advisory",
         ],
         url: "https://projects.eclipse.org/projects/technology.jgit/releases/6.6.1",
      },
   ],
   sourceIdentifier: "emo@eclipse.org",
   vulnStatus: "Modified",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-59",
            },
            {
               lang: "en",
               value: "CWE-178",
            },
         ],
         source: "emo@eclipse.org",
         type: "Secondary",
      },
      {
         description: [
            {
               lang: "en",
               value: "CWE-59",
            },
            {
               lang: "en",
               value: "CWE-178",
            },
         ],
         source: "nvd@nist.gov",
         type: "Primary",
      },
   ],
}


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.