CVE-2020-26312 (GCVE-0-2020-26312)

Vulnerability from cvelistv5 – Published: 2024-05-14 20:22 – Updated: 2024-08-04 15:56
VLAI
Title
GHSL-2020-254: Arbitrary file read and/or write in dotmesh
Summary
Dotmesh is a git-like command-line interface for capturing, organizing and sharing application states. In versions 0.8.1 and prior, the unsafe handling of symbolic links in an unpacking routine may enable attackers to read and/or write to arbitrary locations outside the designated target folder. The routine `untarFile` attempts to guard against creating symbolic links that point outside the directory a tar archive is extracted to. However, a malicious tarball first linking `subdir/parent` to `..` (allowed, because `subdir/..` falls within the archive root) and then linking `subdir/parent/escapes` to `..` results in a symbolic link pointing to the tarball’s parent directory, contrary to the routine’s goals. This issue may lead to arbitrary file write (with same permissions as the program running the unpack operation) if the attacker can control the archive file. Additionally, if the attacker has read access to the unpacked files, they may be able to read arbitrary system files the parent process has permissions to read. As of time of publication, no patch for this issue is available.
CWE
Assigner
Impacted products
Vendor Product Version
dotmesh-io dotmesh Affected: 0 , ≤ 0.8.1 (custom)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "affected": [
          {
            "cpes": [
              "cpe:2.3:a:dotmesh-io:dotmesh:*:*:*:*:*:*:*:*"
            ],
            "defaultStatus": "unknown",
            "product": "dotmesh",
            "vendor": "dotmesh-io",
            "versions": [
              {
                "lessThanOrEqual": "0.8.1",
                "status": "affected",
                "version": "0",
                "versionType": "custom"
              }
            ]
          }
        ],
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2020-26312",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-05-15T15:03:53.759790Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-06-05T18:02:30.164Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-04T15:56:04.289Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://securitylab.github.com/advisories/GHSL-2020-254-zipslip-dotmesh/"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://github.com/dotmesh-io/dotmesh/blob/master/pkg/archiver/tar.go#L255"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageName": "dotmesh",
          "product": "dotmesh",
          "repo": "https://github.com/dotmesh-io/dotmesh",
          "vendor": "dotmesh-io",
          "versions": [
            {
              "lessThanOrEqual": "0.8.1",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Dotmesh is a git-like command-line interface for capturing, organizing and sharing application states. In versions 0.8.1 and prior, the unsafe handling of symbolic links in an unpacking routine may \nenable attackers to read and/or write to arbitrary locations outside the\n designated target folder.\u0026nbsp;The routine `untarFile` attempts to guard against creating symbolic links that point outside the directory a tar archive is extracted to. However, a malicious tarball first linking `subdir/parent` to `..` (allowed, because `subdir/..` falls within the archive root) and then linking `subdir/parent/escapes` to `..` results in a symbolic link pointing to the tarball\u2019s parent directory, contrary to the routine\u2019s goals. This issue may lead to arbitrary file write (with same permissions as the program running the unpack operation) if the attacker can control the archive file. Additionally, if the attacker has read access to the unpacked files, they may be able to read arbitrary system files the parent process has permissions to read. As of time of publication, no patch for this issue is available.\u003cbr\u003e"
            }
          ],
          "value": "Dotmesh is a git-like command-line interface for capturing, organizing and sharing application states. In versions 0.8.1 and prior, the unsafe handling of symbolic links in an unpacking routine may \nenable attackers to read and/or write to arbitrary locations outside the\n designated target folder.\u00a0The routine `untarFile` attempts to guard against creating symbolic links that point outside the directory a tar archive is extracted to. However, a malicious tarball first linking `subdir/parent` to `..` (allowed, because `subdir/..` falls within the archive root) and then linking `subdir/parent/escapes` to `..` results in a symbolic link pointing to the tarball\u2019s parent directory, contrary to the routine\u2019s goals. This issue may lead to arbitrary file write (with same permissions as the program running the unpack operation) if the attacker can control the archive file. Additionally, if the attacker has read access to the unpacked files, they may be able to read arbitrary system files the parent process has permissions to read. As of time of publication, no patch for this issue is available.\n"
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 8.1,
            "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:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-787",
              "description": "CWE-787 Out-of-bounds Write",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-125",
              "description": "CWE-125 Out-of-bounds Read",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-05-14T20:22:04.485Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "url": "https://securitylab.github.com/advisories/GHSL-2020-254-zipslip-dotmesh/"
        },
        {
          "url": "https://github.com/dotmesh-io/dotmesh/blob/master/pkg/archiver/tar.go#L255"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "GHSL-2020-254: Arbitrary file read and/or write in dotmesh",
      "x_generator": {
        "engine": "Vulnogram 0.1.0-dev"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2020-26312",
    "datePublished": "2024-05-14T20:22:04.485Z",
    "dateReserved": "2020-10-01T00:00:00.000Z",
    "dateUpdated": "2024-08-04T15:56:04.289Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2020-26312",
      "date": "2026-05-31",
      "epss": "0.00279",
      "percentile": "0.51456"
    },
    "fkie_nvd": {
      "descriptions": "[{\"lang\": \"en\", \"value\": \"Dotmesh is a git-like command-line interface for capturing, organizing and sharing application states. In versions 0.8.1 and prior, the unsafe handling of symbolic links in an unpacking routine may \\nenable attackers to read and/or write to arbitrary locations outside the\\n designated target folder.\\u00a0The routine `untarFile` attempts to guard against creating symbolic links that point outside the directory a tar archive is extracted to. However, a malicious tarball first linking `subdir/parent` to `..` (allowed, because `subdir/..` falls within the archive root) and then linking `subdir/parent/escapes` to `..` results in a symbolic link pointing to the tarball\\u2019s parent directory, contrary to the routine\\u2019s goals. This issue may lead to arbitrary file write (with same permissions as the program running the unpack operation) if the attacker can control the archive file. Additionally, if the attacker has read access to the unpacked files, they may be able to read arbitrary system files the parent process has permissions to read. As of time of publication, no patch for this issue is available.\\n\"}, {\"lang\": \"es\", \"value\": \"Dotmesh es una interfaz de l\\u00ednea de comandos similar a git para capturar, organizar y compartir estados de aplicaciones. En las versiones 0.8.1 y anteriores, el manejo inseguro de enlaces simb\\u00f3licos en una rutina de descompresi\\u00f3n puede permitir a los atacantes leer y/o escribir en ubicaciones arbitrarias fuera de la carpeta de destino designada. La rutina `untarFile` intenta evitar la creaci\\u00f3n de enlaces simb\\u00f3licos que apunten fuera del directorio al que se extrae un archivo tar. Sin embargo, un tarball malicioso que primero vincula `subdir/parent` a `..` (permitido, porque `subdir/..` se encuentra dentro de la ra\\u00edz del archivo) y luego vincula `subdir/parent/escapes` a `..` da como resultado un enlace simb\\u00f3lico que apunta al directorio principal del tarball, contrario a los objetivos de la rutina. Este problema puede provocar la escritura arbitraria de archivos (con los mismos permisos que el programa que ejecuta la operaci\\u00f3n de descomprimir) si el atacante puede controlar el archivo comprimido. Adem\\u00e1s, si el atacante tiene acceso de lectura a los archivos descomprimidos, es posible que pueda leer archivos arbitrarios del sistema para los que el proceso principal tiene permisos de lectura. Al momento de la publicaci\\u00f3n, no hay ning\\u00fan parche disponible para este problema.\"}]",
      "id": "CVE-2020-26312",
      "lastModified": "2024-11-21T05:19:50.507",
      "metrics": "{\"cvssMetricV31\": [{\"source\": \"security-advisories@github.com\", \"type\": \"Secondary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N\", \"baseScore\": 8.1, \"baseSeverity\": \"HIGH\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"HIGH\", \"integrityImpact\": \"HIGH\", \"availabilityImpact\": \"NONE\"}, \"exploitabilityScore\": 2.8, \"impactScore\": 5.2}]}",
      "published": "2024-05-14T21:15:10.587",
      "references": "[{\"url\": \"https://github.com/dotmesh-io/dotmesh/blob/master/pkg/archiver/tar.go#L255\", \"source\": \"security-advisories@github.com\"}, {\"url\": \"https://securitylab.github.com/advisories/GHSL-2020-254-zipslip-dotmesh/\", \"source\": \"security-advisories@github.com\"}, {\"url\": \"https://github.com/dotmesh-io/dotmesh/blob/master/pkg/archiver/tar.go#L255\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://securitylab.github.com/advisories/GHSL-2020-254-zipslip-dotmesh/\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Awaiting Analysis",
      "weaknesses": "[{\"source\": \"security-advisories@github.com\", \"type\": \"Secondary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-125\"}, {\"lang\": \"en\", \"value\": \"CWE-787\"}]}]"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2020-26312\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2024-05-14T21:15:10.587\",\"lastModified\":\"2024-11-21T05:19:50.507\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Dotmesh is a git-like command-line interface for capturing, organizing and sharing application states. In versions 0.8.1 and prior, the unsafe handling of symbolic links in an unpacking routine may \\nenable attackers to read and/or write to arbitrary locations outside the\\n designated target folder.\u00a0The routine `untarFile` attempts to guard against creating symbolic links that point outside the directory a tar archive is extracted to. However, a malicious tarball first linking `subdir/parent` to `..` (allowed, because `subdir/..` falls within the archive root) and then linking `subdir/parent/escapes` to `..` results in a symbolic link pointing to the tarball\u2019s parent directory, contrary to the routine\u2019s goals. This issue may lead to arbitrary file write (with same permissions as the program running the unpack operation) if the attacker can control the archive file. Additionally, if the attacker has read access to the unpacked files, they may be able to read arbitrary system files the parent process has permissions to read. As of time of publication, no patch for this issue is available.\\n\"},{\"lang\":\"es\",\"value\":\"Dotmesh es una interfaz de l\u00ednea de comandos similar a git para capturar, organizar y compartir estados de aplicaciones. En las versiones 0.8.1 y anteriores, el manejo inseguro de enlaces simb\u00f3licos en una rutina de descompresi\u00f3n puede permitir a los atacantes leer y/o escribir en ubicaciones arbitrarias fuera de la carpeta de destino designada. La rutina `untarFile` intenta evitar la creaci\u00f3n de enlaces simb\u00f3licos que apunten fuera del directorio al que se extrae un archivo tar. Sin embargo, un tarball malicioso que primero vincula `subdir/parent` a `..` (permitido, porque `subdir/..` se encuentra dentro de la ra\u00edz del archivo) y luego vincula `subdir/parent/escapes` a `..` da como resultado un enlace simb\u00f3lico que apunta al directorio principal del tarball, contrario a los objetivos de la rutina. Este problema puede provocar la escritura arbitraria de archivos (con los mismos permisos que el programa que ejecuta la operaci\u00f3n de descomprimir) si el atacante puede controlar el archivo comprimido. Adem\u00e1s, si el atacante tiene acceso de lectura a los archivos descomprimidos, es posible que pueda leer archivos arbitrarios del sistema para los que el proceso principal tiene permisos de lectura. Al momento de la publicaci\u00f3n, no hay ning\u00fan parche disponible para este problema.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N\",\"baseScore\":8.1,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":2.8,\"impactScore\":5.2}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-125\"},{\"lang\":\"en\",\"value\":\"CWE-787\"}]}],\"references\":[{\"url\":\"https://github.com/dotmesh-io/dotmesh/blob/master/pkg/archiver/tar.go#L255\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://securitylab.github.com/advisories/GHSL-2020-254-zipslip-dotmesh/\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/dotmesh-io/dotmesh/blob/master/pkg/archiver/tar.go#L255\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://securitylab.github.com/advisories/GHSL-2020-254-zipslip-dotmesh/\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://securitylab.github.com/advisories/GHSL-2020-254-zipslip-dotmesh/\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://github.com/dotmesh-io/dotmesh/blob/master/pkg/archiver/tar.go#L255\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-04T15:56:04.289Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2020-26312\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"poc\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-05-15T15:03:53.759790Z\"}}}], \"affected\": [{\"cpes\": [\"cpe:2.3:a:dotmesh-io:dotmesh:*:*:*:*:*:*:*:*\"], \"vendor\": \"dotmesh-io\", \"product\": \"dotmesh\", \"versions\": [{\"status\": \"affected\", \"version\": \"0\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"0.8.1\"}], \"defaultStatus\": \"unknown\"}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-05-15T15:06:10.603Z\"}}], \"cna\": {\"title\": \"GHSL-2020-254: Arbitrary file read and/or write in dotmesh\", \"source\": {\"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"format\": \"CVSS\", \"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 8.1, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N\", \"integrityImpact\": \"HIGH\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"HIGH\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"repo\": \"https://github.com/dotmesh-io/dotmesh\", \"vendor\": \"dotmesh-io\", \"product\": \"dotmesh\", \"versions\": [{\"status\": \"affected\", \"version\": \"0\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"0.8.1\"}], \"packageName\": \"dotmesh\", \"defaultStatus\": \"unaffected\"}], \"references\": [{\"url\": \"https://securitylab.github.com/advisories/GHSL-2020-254-zipslip-dotmesh/\"}, {\"url\": \"https://github.com/dotmesh-io/dotmesh/blob/master/pkg/archiver/tar.go#L255\"}], \"x_generator\": {\"engine\": \"Vulnogram 0.1.0-dev\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"Dotmesh is a git-like command-line interface for capturing, organizing and sharing application states. In versions 0.8.1 and prior, the unsafe handling of symbolic links in an unpacking routine may \\nenable attackers to read and/or write to arbitrary locations outside the\\n designated target folder.\\u00a0The routine `untarFile` attempts to guard against creating symbolic links that point outside the directory a tar archive is extracted to. However, a malicious tarball first linking `subdir/parent` to `..` (allowed, because `subdir/..` falls within the archive root) and then linking `subdir/parent/escapes` to `..` results in a symbolic link pointing to the tarball\\u2019s parent directory, contrary to the routine\\u2019s goals. This issue may lead to arbitrary file write (with same permissions as the program running the unpack operation) if the attacker can control the archive file. Additionally, if the attacker has read access to the unpacked files, they may be able to read arbitrary system files the parent process has permissions to read. As of time of publication, no patch for this issue is available.\\n\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Dotmesh is a git-like command-line interface for capturing, organizing and sharing application states. In versions 0.8.1 and prior, the unsafe handling of symbolic links in an unpacking routine may \\nenable attackers to read and/or write to arbitrary locations outside the\\n designated target folder.\u0026nbsp;The routine `untarFile` attempts to guard against creating symbolic links that point outside the directory a tar archive is extracted to. However, a malicious tarball first linking `subdir/parent` to `..` (allowed, because `subdir/..` falls within the archive root) and then linking `subdir/parent/escapes` to `..` results in a symbolic link pointing to the tarball\\u2019s parent directory, contrary to the routine\\u2019s goals. This issue may lead to arbitrary file write (with same permissions as the program running the unpack operation) if the attacker can control the archive file. Additionally, if the attacker has read access to the unpacked files, they may be able to read arbitrary system files the parent process has permissions to read. As of time of publication, no patch for this issue is available.\u003cbr\u003e\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-787\", \"description\": \"CWE-787 Out-of-bounds Write\"}]}, {\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-125\", \"description\": \"CWE-125 Out-of-bounds Read\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2024-05-14T20:22:04.485Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2020-26312\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-08-04T15:56:04.289Z\", \"dateReserved\": \"2020-10-01T00:00:00.000Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2024-05-14T20:22:04.485Z\", \"assignerShortName\": \"GitHub_M\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.1"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…