Vulnerability from bitnami_vulndb
Published
2024-05-24 07:18
Modified
2026-01-07 12:31
Summary
Cloning local Git repository by untrusted user allows the untrusted user to modify objects in the cloned repository at will
Details

Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository's object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a "proper" clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "git",
        "purl": "pkg:bitnami/git"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.39.4"
            },
            {
              "introduced": "2.40.0"
            },
            {
              "fixed": "2.40.2"
            },
            {
              "introduced": "2.41.0"
            },
            {
              "fixed": "2.41.1"
            },
            {
              "introduced": "2.42.0"
            },
            {
              "fixed": "2.42.2"
            },
            {
              "introduced": "2.43.0"
            },
            {
              "fixed": "2.43.4"
            },
            {
              "introduced": "2.44.0"
            },
            {
              "fixed": "2.44.1"
            },
            {
              "introduced": "2.45.0"
            },
            {
              "fixed": "2.45.1"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "severity": [
        {
          "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
          "type": "CVSS_V3"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-32020"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:git:git:*:*:*:*:*:*:*:*"
    ],
    "severity": "Low"
  },
  "details": "Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository\u0027s object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a \"proper\" clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.",
  "id": "BIT-git-2024-32020",
  "modified": "2026-01-07T12:31:01.344Z",
  "published": "2024-05-24T07:18:47.345Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/git/git/commit/1204e1a824c34071019fe106348eaa6d88f9528d"
    },
    {
      "type": "WEB",
      "url": "https://github.com/git/git/commit/9e65df5eab274bf74c7b570107aacd1303a1e703"
    },
    {
      "type": "WEB",
      "url": "https://github.com/git/git/security/advisories/GHSA-5rfh-556j-fhgj"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2024/05/14/2"
    },
    {
      "type": "WEB",
      "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-32020"
    }
  ],
  "schema_version": "1.5.0",
  "summary": "Cloning local Git repository by untrusted user allows the untrusted user to modify objects in the cloned repository at will"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.