CVE-2014-9390: n/a vulnerability

CVE-2014-9390: Git before 1.8.5.6, 1.9.x before 1.9.5, 2.0.x before 2.0.5, 2.1.x before 2.1.4, and 2.2.x before 2.2.1 on W...

Git before 1.8.5.6, 1.9.x before 1.9.5, 2.0.x before 2.0.5, 2.1.x before 2.1.4, and 2.2.x before 2.2.1 on Windows and OS X; Mercurial before 3.2.3 on Windows and OS X; Apple Xcode before 6.2 beta 3; mine all versions before 08-12-2014; libgit2 all versions up to 0.21.2; Egit all versions before 08-12-2014; and JGit all versions before 08-12-2014 allow remote Git servers to execute arbitrary commands via a tree containing a crafted .git/config file with (1) an ignorable Unicode codepoint, (2) a git~1/config representation, or (3) mixed case that is improperly handled on a case-insensitive filesystem.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 13:40 UTC (UTC+00:00)

Security readout for executives and security teams

A malicious repository can abuse how some Windows and OS X clients treated paths that looked like .git/config. In affected Git, Mercurial, Xcode, libgit2, EGit, JGit, and related tools, this could let a remote Git server trigger arbitrary commands on developer machines or build systems. Exposure is most likely on legacy Windows or OS X developer workstations, CI runners, build agents, IDEs, or applications using old Git-compatible libraries to fetch untrusted repositories. Prioritize remediation where old developer tooling or build infrastructure may process third-party repositories. The business risk is supply-chain compromise through developer endpoints, not broad internet-facing server exposure. Mitigation focus: Upgrade Git to the fixed version for the deployed release line or newer.; Upgrade Mercurial to 3.2.3 or newer where used on Windows or OS X.; Update Apple Xcode to a version including the referenced security fix..

Prepared: Jun 6, 2026, 02:28 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2014-9390 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Feb 12, 2020, 01:58 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://news.ycombinator.com/item?id=8769667CVE reference · x_refsource_MISC
https://github.com/blog/1938-git-client-vulnerability-announcedCVE reference · x_refsource_MISC
https://github.com/libgit2/libgit2/commit/928429c5c96a701bcbcafacb2421a82602b36915CVE reference · x_refsource_MISC
https://libgit2.org/security/CVE reference · x_refsource_MISC

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.