GSD-2015-8968

Vulnerability from gsd - Updated: 2015-12-11 00:00
Details
Git allows executing arbitrary shell commands using git-remote-ext via a remote URLs. Normally git never requests URLs that the user doesn't specifically request, so this is not a serious security concern. However, submodules did allow the remote repository to specify what URL to clone from. If an attacker can instruct a user to run a recursive clone from a repository they control, they can get a client to run an arbitrary shell command. Alternately, if an attacker can MITM an unencrypted git clone, they could exploit this. The ext command will be run if the repository is recursively cloned or if submodules are updated. This attack works when cloning both local and remote repositories.
Aliases
Aliases
CVE-2015-8968
To clipboard 

{
  "GSD": {
    "alias": "CVE-2015-8968",
    "description": "git-fastclone before 1.0.1 permits arbitrary shell command execution from .gitmodules. If an attacker can instruct a user to run a recursive clone from a repository they control, they can get a client to run an arbitrary shell command. Alternately, if an attacker can MITM an unencrypted git clone, they could exploit this. The ext command will be run if the repository is recursively cloned or if submodules are updated. This attack works when cloning both local and remote repositories.",
    "id": "GSD-2015-8968"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "affected": [
        {
          "package": {
            "ecosystem": "RubyGems",
            "name": "git-fastclone",
            "purl": "pkg:gem/git-fastclone"
          }
        }
      ],
      "aliases": [
        "CVE-2015-8968",
        "GHSA-8gg6-3r63-25m8"
      ],
      "details": "Git allows executing arbitrary shell commands using git-remote-ext via a\nremote URLs. Normally git never requests URLs that the user doesn\u0027t\nspecifically request, so this is not a serious security concern. However,\nsubmodules did allow the remote repository to specify what URL to clone\nfrom.\n\nIf an attacker can instruct a user to run a recursive clone from a\nrepository they control, they can get a client to run an arbitrary shell\ncommand. Alternately, if an attacker can MITM an unencrypted git clone,\nthey could exploit this. The ext command will be run if the repository is\nrecursively cloned or if submodules are updated. This attack works when\ncloning both local and remote repositories.\n",
      "id": "GSD-2015-8968",
      "modified": "2015-12-11T00:00:00.000Z",
      "published": "2015-12-11T00:00:00.000Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://hackerone.com/reports/104465"
        }
      ],
      "schema_version": "1.4.0",
      "severity": [
        {
          "score": 8.8,
          "type": "CVSS_V3"
        }
      ],
      "summary": "git-fastclone permits arbitrary shell command execution from .gitmodules"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "support@hackerone.com",
        "ID": "CVE-2015-8968",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "git-fastclone ruby gem All versions before 1.0.1",
                    "version": {
                      "version_data": [
                        {
                          "version_value": "git-fastclone ruby gem All versions before 1.0.1"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "n/a"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "git-fastclone before 1.0.1 permits arbitrary shell command execution from .gitmodules. If an attacker can instruct a user to run a recursive clone from a repository they control, they can get a client to run an arbitrary shell command. Alternately, if an attacker can MITM an unencrypted git clone, they could exploit this. The ext command will be run if the repository is recursively cloned or if submodules are updated. This attack works when cloning both local and remote repositories."
          }
        ]
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "lang": "eng",
                "value": "Arbitrary Command Execution"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://hackerone.com/reports/104465",
            "refsource": "MISC",
            "url": "https://hackerone.com/reports/104465"
          },
          {
            "name": "81433",
            "refsource": "BID",
            "url": "http://www.securityfocus.com/bid/81433"
          },
          {
            "name": "https://github.com/square/git-fastclone/pull/2",
            "refsource": "MISC",
            "url": "https://github.com/square/git-fastclone/pull/2"
          }
        ]
      }
    },
    "github.com/rubysec/ruby-advisory-db": {
      "cve": "2015-8968",
      "cvss_v3": 8.8,
      "date": "2015-12-11",
      "description": "Git allows executing arbitrary shell commands using git-remote-ext via a\nremote URLs. Normally git never requests URLs that the user doesn\u0027t\nspecifically request, so this is not a serious security concern. However,\nsubmodules did allow the remote repository to specify what URL to clone\nfrom.\n\nIf an attacker can instruct a user to run a recursive clone from a\nrepository they control, they can get a client to run an arbitrary shell\ncommand. Alternately, if an attacker can MITM an unencrypted git clone,\nthey could exploit this. The ext command will be run if the repository is\nrecursively cloned or if submodules are updated. This attack works when\ncloning both local and remote repositories.\n",
      "gem": "git-fastclone",
      "ghsa": "8gg6-3r63-25m8",
      "patched_versions": [
        "\u003e= 1.0.1"
      ],
      "title": "git-fastclone permits arbitrary shell command execution from .gitmodules",
      "url": "https://hackerone.com/reports/104465"
    },
    "gitlab.com": {
      "advisories": [
        {
          "affected_range": "\u003c1.0.1",
          "affected_versions": "All versions before 1.0.1",
          "credit": "Blake Burkhart",
          "cvss_v2": "AV:N/AC:M/Au:N/C:C/I:C/A:C",
          "cvss_v3": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
          "cwe_ids": [
            "CWE-1035",
            "CWE-77",
            "CWE-937"
          ],
          "date": "2016-11-28",
          "description": " Git allows executing arbitrary shell commands using `git-remote-ext` via remote\nURLs. Normally git never requests URLs that the user does not specifically request, so this is not a serious security concern. However, submodules did allow the remote repository to specify what URL to clone from. If an attacker can instruct a user to run a recursive clone from a repository they control, they can get a client to run an arbitrary shell command. Alternately, if an attacker can MITM an unencrypted git clone, they could exploit this. The ext command will be run if the repository is recursively cloned or if submodules are updated. This attack works when cloning both local and remote repositories.",
          "fixed_versions": [
            "1.0.1"
          ],
          "identifier": "CVE-2015-8968",
          "identifiers": [
            "CVE-2015-8968"
          ],
          "not_impacted": "All versions starting from 1.0.1",
          "package_slug": "gem/git-fastclone",
          "pubdate": "2016-11-03",
          "solution": "Upgrade to version 1.0.1 or above.",
          "title": "Arbitrary shell command execution from .gitmodules",
          "urls": [
            "https://github.com/square/git-fastclone/pull/2",
            "https://hackerone.com/reports/104465"
          ],
          "uuid": "4fe98f18-52d8-4aeb-8412-180c715ab574"
        }
      ]
    },
    "nvd.nist.gov": {
      "configurations": {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:a:squareup:git-fastclone:*:*:*:*:*:*:*:*",
                "cpe_name": [],
                "versionEndExcluding": "1.0.1",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      },
      "cve": {
        "CVE_data_meta": {
          "ASSIGNER": "cve-assignments@hackerone.com",
          "ID": "CVE-2015-8968"
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "en",
              "value": "git-fastclone before 1.0.1 permits arbitrary shell command execution from .gitmodules. If an attacker can instruct a user to run a recursive clone from a repository they control, they can get a client to run an arbitrary shell command. Alternately, if an attacker can MITM an unencrypted git clone, they could exploit this. The ext command will be run if the repository is recursively cloned or if submodules are updated. This attack works when cloning both local and remote repositories."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "en",
                  "value": "CWE-77"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://github.com/square/git-fastclone/pull/2",
              "refsource": "MISC",
              "tags": [
                "Patch",
                "Vendor Advisory"
              ],
              "url": "https://github.com/square/git-fastclone/pull/2"
            },
            {
              "name": "https://hackerone.com/reports/104465",
              "refsource": "MISC",
              "tags": [
                "Exploit",
                "Third Party Advisory"
              ],
              "url": "https://hackerone.com/reports/104465"
            },
            {
              "name": "81433",
              "refsource": "BID",
              "tags": [
                "Third Party Advisory",
                "VDB Entry"
              ],
              "url": "http://www.securityfocus.com/bid/81433"
            }
          ]
        }
      },
      "impact": {
        "baseMetricV2": {
          "cvssV2": {
            "accessComplexity": "MEDIUM",
            "accessVector": "NETWORK",
            "authentication": "NONE",
            "availabilityImpact": "COMPLETE",
            "baseScore": 9.3,
            "confidentialityImpact": "COMPLETE",
            "integrityImpact": "COMPLETE",
            "vectorString": "AV:N/AC:M/Au:N/C:C/I:C/A:C",
            "version": "2.0"
          },
          "exploitabilityScore": 8.6,
          "impactScore": 10.0,
          "obtainAllPrivilege": false,
          "obtainOtherPrivilege": false,
          "obtainUserPrivilege": false,
          "severity": "HIGH",
          "userInteractionRequired": true
        },
        "baseMetricV3": {
          "cvssV3": {
            "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
        }
      },
      "lastModifiedDate": "2020-06-10T13:24Z",
      "publishedDate": "2016-11-03T10:59Z"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.