# CVE-2014-9390: JGit Improper Input Validation vulnerability

Source: https://junglewise.ai/threats/cve-2014-9390-jgit-improper-input-validation-vulnerability  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2020-02-12  
License: CC BY 4.0 with a link back

CVE-2014-9390 · Severity: low · CVSS 3.1 · Published 2020-02-12

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.

Technologies: [org.eclipse.jgit:org.eclipse.jgit (Maven)](https://junglewise.ai/threats/technologies/org-eclipse-jgit-org-eclipse-jgit), [mercurial (PyPI)](https://junglewise.ai/threats/technologies/mercurial). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven), [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2014-9390 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2014-9390 being exploited in the wild.

**How severe is CVE-2014-9390?** Low severity, with a CVSS score of 3.1, published 12 February 2020.

**Which products and versions are affected?** org.eclipse.jgit:org.eclipse.jgit (Maven) ECOSYSTEM:introduced=0,fixed=3.5.3; mercurial (PyPI) ECOSYSTEM:introduced=0,fixed=3.2.3.

**Is there a fix for CVE-2014-9390?** Yes. org.eclipse.jgit:org.eclipse.jgit (Maven): upgrade to 3.5.3 or later; mercurial (PyPI): upgrade to 3.2.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2014-9390?** Check whether you run org.eclipse.jgit:org.eclipse.jgit (Maven) or mercurial (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.eclipse.jgit:org.eclipse.jgit (Maven): upgrade to 3.5.3 or later

  ```sh
  # set org.eclipse.jgit:org.eclipse.jgit to 3.5.3 in your pom.xml or build.gradle
  ```

- mercurial (PyPI): upgrade to 3.2.3 or later

  ```sh
  pip install "mercurial>=3.2.3"
  ```


## Affected products

- org.eclipse.jgit:org.eclipse.jgit (Maven) ECOSYSTEM:introduced=0,fixed=3.5.3
- mercurial (PyPI) ECOSYSTEM:introduced=0,fixed=3.2.3

## Identifiers

- CVE-2014-9390
- GHSA-6vvc-c2m3-cjf3
- PYSEC-2020-217

## Related threats

- [PYSEC-2026-666 - Mercurial Directory traversal vulnerability](https://junglewise.ai/threats/cve-2008-2942-mercurial-directory-traversal-vulnerability)
- [PYSEC-2026-665 - Mercurial Improper Certificate Validation vulnerability](https://junglewise.ai/threats/cve-2010-4237-mercurial-improper-certificate-validation-vulnerability)
- [Eclipse JGit XML External Entity (XXE) Vulnerability](https://junglewise.ai/threats/cve-2025-4949-eclipse-jgit-xml-external-entity-xxe-vulnerability)
- [Arbitrary File Overwrite in Eclipse JGit](https://junglewise.ai/threats/cve-2023-4759-arbitrary-file-overwrite-in-eclipse-jgit)
- [Mercurial Path Traversal/Link Following vulnerability](https://junglewise.ai/threats/cve-2019-3902-mercurial-path-traversal-link-following-vulnerability)