CVE-2020-26233

{"id": "CVE-2020-26233", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 3.6, "accessVector": "NETWORK", "vectorString": "AV:N/AC:H/Au:S/C:P/I:P/A:N", "authentication": "SINGLE", "integrityImpact": "PARTIAL", "accessComplexity": "HIGH", "availabilityImpact": "NONE", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 4.9, "baseSeverity": "LOW", "obtainAllPrivilege": false, "exploitabilityScore": 3.9, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": true}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 7.3, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "HIGH", "confidentialityImpact": "HIGH"}, "impactScore": 5.8, "exploitabilityScore": 1.0}, {"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 7.3, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "HIGH", "confidentialityImpact": "HIGH"}, "impactScore": 5.8, "exploitabilityScore": 1.0}]}, "published": "2020-12-08T20:15:15.447", "references": [{"url": "https://blog.blazeinfosec.com/attack-of-the-clones-2-git-command-client-remote-code-execution-strikes-back/", "tags": ["Exploit", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://git-scm.com/docs/git-clone#Documentation/git-clone.txt---recurse-submodulesltpathspecgt", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/microsoft/Git-Credential-Manager-Core/commit/61c0388e064babb3b4e60d3ec269e8a07ab3bc76", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/microsoft/Git-Credential-Manager-Core/releases/tag/v2.0.289-beta", "tags": ["Release Notes", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/microsoft/Git-Credential-Manager-Core/security/advisories/GHSA-2gq7-ww4j-3m76", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-706"}]}, {"type": "Secondary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-706"}]}], "descriptions": [{"lang": "en", "value": "Git Credential Manager Core (GCM Core) is a secure Git credential helper built on .NET Core that runs on Windows and macOS. In Git Credential Manager Core before version 2.0.289, when recursively cloning a Git repository on Windows with submodules, Git will first clone the top-level repository and then recursively clone all submodules by starting new Git processes from the top-level working directory. If a malicious git.exe executable is present in the top-level repository then this binary will be started by Git Credential Manager Core when attempting to read configuration, and not git.exe as found on the %PATH%. This only affects GCM Core on Windows, not macOS or Linux-based distributions. GCM Core version 2.0.289 contains the fix for this vulnerability, and is available from the project's GitHub releases page. GCM Core 2.0.289 is also bundled in the latest Git for Windows release; version 2.29.2(3). As a workaround, users should avoid recursively cloning untrusted repositories with the --recurse-submodules option."}, {"lang": "es", "value": "Git Credential Manager Core (GCM Core) es un asistente de credenciales de Git seguro dise\u00f1ado en .NET Core que se ejecuta en Windows y macOS. En Git Credential Manager Core versiones anteriores a 2.0.289, cuando recursivamente se clona un repositorio de Git en Windows con subm\u00f3dulos, Git primero clonar\u00e1 el repositorio de nivel superior y luego clonar\u00e1 de forma recursiva todos los subm\u00f3dulos iniciando nuevos procesos de Git desde el directorio de trabajo de nivel superior. Si un ejecutable git.exe malicioso est\u00e1 presente en el repositorio de nivel superior, Git Credential Manager Core iniciar\u00e1 este binario cuando intente leer la configuraci\u00f3n, y no git.exe como se encuentra en %PATH%. Esto solo afecta a GCM Core en Windows, no a las distribuciones basadas en macOS o Linux. GCM Core versi\u00f3n 2.0.289 contiene la correcci\u00f3n para esta vulnerabilidad y est\u00e1 disponible desde la p\u00e1gina de versiones de GitHub del proyecto. GCM Core versi\u00f3n 2.0.289 tambi\u00e9n se incluye en la \u00faltima versi\u00f3n de Git para Windows; versi\u00f3n 2.29.2(3). Como soluci\u00f3n alternativa, los usuarios deben evitar la clonaci\u00f3n recursiva de repositorios que no sean de confianza con la opci\u00f3n --recurse-submodules"}], "lastModified": "2021-02-18T14:39:02.197", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:microsoft:git_credential_manager_core:*:*:*:*:*:windows:*:*", "vulnerable": true, "matchCriteriaId": "73C1ADBA-6CE0-48E5-8FF4-AC18AE88985C", "versionEndExcluding": "2.0.289"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}