CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCritical (9.8). EPSS 76% estimated probability of exploitation activity in the next 30 days. Fixed in org.eclipse.jgit:org.eclipse.jgit 3.5.3.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Horg.eclipse.jgit:org.eclipse.jgit (Maven): fixed in 3.5.3mercurial (PyPI): fixed in 3.2.3Explain CVE-2014-9390 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2014-9390?via=ask-ai-copy and https://cve.bz/cve/CVE-2014-9390?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2014-9390 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| git-scm:git | before 1.8.5.6 |
| git-scm:git | from 1.9.0 before 1.9.5 |
| git-scm:git | from 2.0.0 before 2.0.5 |
| git-scm:git | from 2.1.0 before 2.1.4 |
| git-scm:git | from 2.2.0 before 2.2.1 |
| mercurial:mercurial | before 3.2.3 |
| apple:xcode | through 6.1.1 |
| apple:xcode | 6.2 |
| apple:xcode | 6.2:beta_2 |
| eclipse:egit | before 08-12-2014 |
| eclipse:jgit | before 3.4.2 |
| eclipse:jgit | from 3.5.0 before 3.5.3 |
| libgit2:libgit2 | before 0.21.3 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-6vvc-c2m3-cjf3 | Maven | org.eclipse.jgit:org.eclipse.jgit | <3.5.3 | 3.5.3 |
| GHSA-6vvc-c2m3-cjf3 | PyPI | mercurial | <3.2.3 | 3.2.3 |
| PYSEC-2020-217 | PyPI | mercurial | <3.2.3 | 3.2.3 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 6.0 | mercurial | 1.6.4-1+deb6u1 | DLA-237-1 |
| Debian | 12, 13, 14 | dulwich | 0.10.1-1 | DEBIAN-CVE-2014-9390 |
| Debian | 12, 13, 14 | git | 1:2.1.4-1 | DEBIAN-CVE-2014-9390 |
| Debian | 12, 13, 14 | jgit | 3.7.0-1 | DEBIAN-CVE-2014-9390 |
| Debian | 12, 13, 14 | libgit2 | 0.21.3-1 | DEBIAN-CVE-2014-9390 |
| Debian | 12, 13, 14 | mercurial | 3.1.2-2 | DEBIAN-CVE-2014-9390 |
| Ubuntu | 14.04:LTS | git | 1:1.9.1-1ubuntu0.1 | UBUNTU-CVE-2014-9390 USN-2470-1 |
| Ubuntu | 14.04:LTS | mercurial | 2.8.2-1ubuntu1.3 | UBUNTU-CVE-2014-9390 |
| Ubuntu | Pro:14.04:LTS | libgit2 | no fix listed | UBUNTU-CVE-2014-9390 |
| openSUSE | Tumbleweed | git | 2.11.0-1.1 | openSUSE-SU-2024:10099-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.
Red Hat rates this Low.
This flaw is only exploitable when the local git repository is stored on a case-insensitive filesystem. By default, Red Hat Enterprise Linux uses case-sensitive filesystems (such as ext2/3/4, XFS, etc.) and as such is not vulnerable to this flaw.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 6 | git | Not affected | |
| Red Hat Enterprise Linux 7 | git | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2014-9390.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).