gsd-2022-39253
Vulnerability from gsd
Modified
2023-12-13 01:19
Details
Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a malicious actor. When performing a local clone (where the source and target of the clone are on the same volume), Git copies the contents of the source's `$GIT_DIR/objects` directory into the destination by either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via `--no-hardlinks`). A malicious actor could convince a victim to clone a repository with a symbolic link pointing at sensitive information on the victim's machine. This can be done either by having the victim clone a malicious repository on the same machine, or having them clone a malicious repository embedded as a bare repository via a submodule from any source, provided they clone with the `--recurse-submodules` option. Git does not create symbolic links in the `$GIT_DIR/objects` directory. The problem has been patched in the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning untrusted repositories using the `--local` optimization when on a shared machine, either by passing the `--no-local` option to `git clone` or cloning from a URL that uses the `file://` scheme. Alternatively, avoid cloning repositories from untrusted sources with `--recurse-submodules` or run `git config --global protocol.file.allow user`.
Aliases
Aliases
{ GSD: { alias: "CVE-2022-39253", description: "Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a malicious actor. When performing a local clone (where the source and target of the clone are on the same volume), Git copies the contents of the source's `$GIT_DIR/objects` directory into the destination by either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via `--no-hardlinks`). A malicious actor could convince a victim to clone a repository with a symbolic link pointing at sensitive information on the victim's machine. This can be done either by having the victim clone a malicious repository on the same machine, or having them clone a malicious repository embedded as a bare repository via a submodule from any source, provided they clone with the `--recurse-submodules` option. Git does not create symbolic links in the `$GIT_DIR/objects` directory. The problem has been patched in the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning untrusted repositories using the `--local` optimization when on a shared machine, either by passing the `--no-local` option to `git clone` or cloning from a URL that uses the `file://` scheme. Alternatively, avoid cloning repositories from untrusted sources with `--recurse-submodules` or run `git config --global protocol.file.allow user`.", id: "GSD-2022-39253", references: [ "https://alas.aws.amazon.com/cve/html/CVE-2022-39253.html", "https://advisories.mageia.org/CVE-2022-39253.html", "https://www.suse.com/security/cve/CVE-2022-39253.html", "https://ubuntu.com/security/CVE-2022-39253", ], }, gsd: { metadata: { exploitCode: "unknown", remediation: "unknown", reportConfidence: "confirmed", type: "vulnerability", }, osvSchema: { aliases: [ "CVE-2022-39253", ], details: "Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a malicious actor. When performing a local clone (where the source and target of the clone are on the same volume), Git copies the contents of the source's `$GIT_DIR/objects` directory into the destination by either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via `--no-hardlinks`). A malicious actor could convince a victim to clone a repository with a symbolic link pointing at sensitive information on the victim's machine. This can be done either by having the victim clone a malicious repository on the same machine, or having them clone a malicious repository embedded as a bare repository via a submodule from any source, provided they clone with the `--recurse-submodules` option. Git does not create symbolic links in the `$GIT_DIR/objects` directory. The problem has been patched in the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning untrusted repositories using the `--local` optimization when on a shared machine, either by passing the `--no-local` option to `git clone` or cloning from a URL that uses the `file://` scheme. Alternatively, avoid cloning repositories from untrusted sources with `--recurse-submodules` or run `git config --global protocol.file.allow user`.", id: "GSD-2022-39253", modified: "2023-12-13T01:19:20.624357Z", schema_version: "1.4.0", }, }, namespaces: { "cve.org": { CVE_data_meta: { ASSIGNER: "security-advisories@github.com", ID: "CVE-2022-39253", STATE: "PUBLIC", TITLE: "Git subject to exposure of sensitive information via local clone of symbolic links", }, affects: { vendor: { vendor_data: [ { product: { product_data: [ { product_name: "git", version: { version_data: [ { version_value: "< 2.30.6", }, { version_value: "< 2.31.5", }, { version_value: "< 2.32.4", }, { version_value: "< 2.33.5", }, { version_value: "< 2.34.5", }, { version_value: "< 2.35.5", }, { version_value: "< 2.36.3", }, { version_value: "< 2.37.4", }, ], }, }, ], }, vendor_name: "git", }, ], }, }, data_format: "MITRE", data_type: "CVE", data_version: "4.0", description: { description_data: [ { lang: "eng", value: "Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a malicious actor. When performing a local clone (where the source and target of the clone are on the same volume), Git copies the contents of the source's `$GIT_DIR/objects` directory into the destination by either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via `--no-hardlinks`). A malicious actor could convince a victim to clone a repository with a symbolic link pointing at sensitive information on the victim's machine. This can be done either by having the victim clone a malicious repository on the same machine, or having them clone a malicious repository embedded as a bare repository via a submodule from any source, provided they clone with the `--recurse-submodules` option. Git does not create symbolic links in the `$GIT_DIR/objects` directory. The problem has been patched in the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning untrusted repositories using the `--local` optimization when on a shared machine, either by passing the `--no-local` option to `git clone` or cloning from a URL that uses the `file://` scheme. Alternatively, avoid cloning repositories from untrusted sources with `--recurse-submodules` or run `git config --global protocol.file.allow user`.", }, ], }, impact: { cvss: { attackComplexity: "LOW", attackVector: "LOCAL", availabilityImpact: "NONE", baseScore: 5.5, baseSeverity: "MEDIUM", confidentialityImpact: "HIGH", integrityImpact: "NONE", privilegesRequired: "NONE", scope: "UNCHANGED", userInteraction: "REQUIRED", vectorString: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N", version: "3.1", }, }, problemtype: { problemtype_data: [ { description: [ { lang: "eng", value: "CWE-200: Exposure of Sensitive Information to an Unauthorized Actor", }, ], }, ], }, references: { reference_data: [ { name: "https://github.com/git/git/security/advisories/GHSA-3wp6-j8xr-qw85", refsource: "CONFIRM", url: "https://github.com/git/git/security/advisories/GHSA-3wp6-j8xr-qw85", }, { name: "FEDORA-2022-12790ca71a", refsource: "FEDORA", url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VFYXCTLOSESYIP72BUYD6ECDIMUM4WMB/", }, { name: "FEDORA-2022-8b58806840", refsource: "FEDORA", url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UKFHE4KVD7EKS5J3KTDFVBEKU3CLXGVV/", }, { name: "https://support.apple.com/kb/HT213496", refsource: "CONFIRM", url: "https://support.apple.com/kb/HT213496", }, { name: "FEDORA-2022-53aadd995f", refsource: "FEDORA", url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OHNO2FB55CPX47BAXMBWUBGWHO6N6ZZH/", }, { name: "20221107 APPLE-SA-2022-11-01-1 Xcode 14.1", refsource: "FULLDISC", url: "http://seclists.org/fulldisclosure/2022/Nov/1", }, { name: "FEDORA-2022-2c33bba286", refsource: "FEDORA", url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JMQWGMDLX6KTVWW5JZLVPI7ICAK72TN7/", }, { name: "FEDORA-2022-fb088df94c", refsource: "FEDORA", url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C7B6JPKX5CGGLAHXJVQMIZNNEEB72FHD/", }, { name: "[debian-lts-announce] 20221213 [SECURITY] [DLA 3239-1] git security update", refsource: "MLIST", url: "https://lists.debian.org/debian-lts-announce/2022/12/msg00025.html", }, { name: "[oss-security] 20230214 [Announce] Git 2.39.2 and friends", refsource: "MLIST", url: "http://www.openwall.com/lists/oss-security/2023/02/14/5", }, { name: "GLSA-202312-15", refsource: "GENTOO", url: "https://security.gentoo.org/glsa/202312-15", }, ], }, source: { advisory: "GHSA-3wp6-j8xr-qw85", discovery: "UNKNOWN", }, }, "nvd.nist.gov": { cve: { configurations: [ { nodes: [ { cpeMatch: [ { criteria: "cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*", matchCriteriaId: "28199E8F-36D0-46F8-AF0A-9460390BE56F", versionEndExcluding: "2.30.6", vulnerable: true, }, { criteria: "cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*", matchCriteriaId: "E095AAE7-18C2-4957-9740-FC804860B9C2", versionEndExcluding: "2.31.5", versionStartIncluding: "2.31.0", vulnerable: true, }, { criteria: "cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*", matchCriteriaId: "459EE43E-40FB-45BE-A1CC-51435E9F92AD", versionEndExcluding: "2.32.4", versionStartIncluding: "2.32.0", vulnerable: true, }, { criteria: "cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*", matchCriteriaId: "2CBDDA42-F5EC-4747-BF3C-16683D684702", versionEndExcluding: "2.33.5", versionStartIncluding: "2.33.0", vulnerable: true, }, { criteria: "cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*", matchCriteriaId: "D7691E22-145E-4D97-A6E0-6515742781B9", versionEndExcluding: "2.34.5", versionStartIncluding: "2.34.0", vulnerable: true, }, { criteria: "cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*", matchCriteriaId: "E02396C2-BB34-4D18-917E-DA56EA7B58B9", versionEndExcluding: "2.35.5", versionStartIncluding: "2.35.0", vulnerable: true, }, { criteria: "cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*", matchCriteriaId: "51BEAEEC-9D9D-4CFE-8958-43BFE87DE501", versionEndExcluding: "2.36.3", versionStartIncluding: "2.36.0", vulnerable: true, }, { criteria: "cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*", matchCriteriaId: "566CF89C-AC39-47D7-B3DE-633B2237F816", versionEndExcluding: "2.37.4", versionStartIncluding: "2.37.0", vulnerable: true, }, { criteria: "cpe:2.3:a:git-scm:git:2.38.0:*:*:*:*:*:*:*", matchCriteriaId: "1AFEECCB-B8DB-4270-A860-C2BA1C7B267C", vulnerable: true, }, ], negate: false, operator: "OR", }, ], }, { nodes: [ { cpeMatch: [ { criteria: "cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*", matchCriteriaId: "80E516C0-98A4-4ADE-B69F-66A772E2BAAA", vulnerable: true, }, { criteria: "cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*", matchCriteriaId: "5C675112-476C-4D7C-BCB9-A2FB2D0BC9FD", vulnerable: true, }, { criteria: "cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*", matchCriteriaId: "E30D0E6F-4AE8-4284-8716-991DFA48CC5D", vulnerable: true, }, ], negate: false, operator: "OR", }, ], }, { nodes: [ { cpeMatch: [ { criteria: "cpe:2.3:a:apple:xcode:*:*:*:*:*:*:*:*", matchCriteriaId: "CECD39AA-41F4-4638-B59A-C5E928B585C3", versionEndExcluding: "14.1", vulnerable: true, }, ], negate: false, operator: "OR", }, ], }, { nodes: [ { cpeMatch: [ { criteria: "cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*", matchCriteriaId: "07B237A9-69A3-4A9C-9DA0-4E06BD37AE73", vulnerable: true, }, ], negate: false, operator: "OR", }, ], }, ], descriptions: [ { lang: "en", value: "Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a malicious actor. When performing a local clone (where the source and target of the clone are on the same volume), Git copies the contents of the source's `$GIT_DIR/objects` directory into the destination by either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via `--no-hardlinks`). A malicious actor could convince a victim to clone a repository with a symbolic link pointing at sensitive information on the victim's machine. This can be done either by having the victim clone a malicious repository on the same machine, or having them clone a malicious repository embedded as a bare repository via a submodule from any source, provided they clone with the `--recurse-submodules` option. Git does not create symbolic links in the `$GIT_DIR/objects` directory. The problem has been patched in the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning untrusted repositories using the `--local` optimization when on a shared machine, either by passing the `--no-local` option to `git clone` or cloning from a URL that uses the `file://` scheme. Alternatively, avoid cloning repositories from untrusted sources with `--recurse-submodules` or run `git config --global protocol.file.allow user`.", }, { lang: "es", value: "Git es un sistema de control de revisiones distribuido, escalable y de cĂłdigo abierto. Las versiones anteriores a la 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3 y 2.37.4 están sujetas a una exposiciĂłn de informaciĂłn confidencial a un actor malicioso. Cuando es llevado a cabo un clon local (en el que el origen y el destino del clon están en el mismo volumen), Git copia el contenido del directorio \"$GIT_DIR/objects\" del origen en el destino creando enlaces duros al contenido del origen o copiándolo (si los enlaces duros están deshabilitados por medio de \"--no-hardlinks\"). Un actor malicioso podrĂa convencer a una vĂctima de clonar un repositorio con un enlace simbĂłlico que apunte a informaciĂłn confidencial en la máquina de la vĂctima. Esto puede hacerse ya sea que la vĂctima clone un repositorio malicioso en la misma máquina, o haciendo que clone un repositorio malicioso insertado como repositorio desnudo por medio de un submĂłdulo de cualquier fuente, siempre que clone con la opciĂłn \"--recurse-submodules\". Git no crea enlaces simbĂłlicos en el directorio \"$GIT_DIR/objects\". El problema ha sido parcheado en las versiones publicadas el 18-10-2022, y retrocedido a v2.30.x. Posibles mitigaciones: Evite clonar repositorios no confiables usando la optimizaciĂłn \"--local\" cuando estĂ© en una máquina compartida, ya sea pasando la opciĂłn \"--no-local\" a \"git clone\" o clonando desde una URL que use el esquema \"file://\". Alternativamente, evita clonar repositorios de fuentes no confiables con \"--recurse-submodules\" o ejecuta \"git config --global protocol.file.allow user\"", }, ], id: "CVE-2022-39253", lastModified: "2023-12-27T10:15:37.640", metrics: { cvssMetricV31: [ { cvssData: { attackComplexity: "LOW", attackVector: "LOCAL", availabilityImpact: "NONE", baseScore: 5.5, baseSeverity: "MEDIUM", confidentialityImpact: "HIGH", integrityImpact: "NONE", privilegesRequired: "NONE", scope: "UNCHANGED", userInteraction: "REQUIRED", vectorString: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N", version: "3.1", }, exploitabilityScore: 1.8, impactScore: 3.6, source: "nvd@nist.gov", type: "Primary", }, { cvssData: { attackComplexity: "LOW", attackVector: "LOCAL", availabilityImpact: "NONE", baseScore: 5.5, baseSeverity: "MEDIUM", confidentialityImpact: "HIGH", integrityImpact: "NONE", privilegesRequired: "NONE", scope: "UNCHANGED", userInteraction: "REQUIRED", vectorString: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N", version: "3.1", }, exploitabilityScore: 1.8, impactScore: 3.6, source: "security-advisories@github.com", type: "Secondary", }, ], }, published: "2022-10-19T11:15:11.227", references: [ { source: "security-advisories@github.com", tags: [ "Mailing List", "Third Party Advisory", ], url: "http://seclists.org/fulldisclosure/2022/Nov/1", }, { source: "security-advisories@github.com", tags: [ "Mailing List", "Third Party Advisory", ], url: "http://www.openwall.com/lists/oss-security/2023/02/14/5", }, { source: "security-advisories@github.com", tags: [ "Mitigation", "Third Party Advisory", ], url: "https://github.com/git/git/security/advisories/GHSA-3wp6-j8xr-qw85", }, { source: "security-advisories@github.com", tags: [ "Mailing List", "Third Party Advisory", ], url: "https://lists.debian.org/debian-lts-announce/2022/12/msg00025.html", }, { source: "security-advisories@github.com", url: "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/C7B6JPKX5CGGLAHXJVQMIZNNEEB72FHD/", }, { source: "security-advisories@github.com", url: "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JMQWGMDLX6KTVWW5JZLVPI7ICAK72TN7/", }, { source: "security-advisories@github.com", url: "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OHNO2FB55CPX47BAXMBWUBGWHO6N6ZZH/", }, { source: "security-advisories@github.com", url: "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UKFHE4KVD7EKS5J3KTDFVBEKU3CLXGVV/", }, { source: "security-advisories@github.com", url: "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VFYXCTLOSESYIP72BUYD6ECDIMUM4WMB/", }, { source: "security-advisories@github.com", url: "https://security.gentoo.org/glsa/202312-15", }, { source: "security-advisories@github.com", tags: [ "Third Party Advisory", ], url: "https://support.apple.com/kb/HT213496", }, ], sourceIdentifier: "security-advisories@github.com", vulnStatus: "Modified", weaknesses: [ { description: [ { lang: "en", value: "CWE-59", }, ], source: "nvd@nist.gov", type: "Primary", }, { description: [ { lang: "en", value: "CWE-200", }, ], source: "security-advisories@github.com", type: "Secondary", }, ], }, }, }, }
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.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
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.