JGit Improper Input Validation vulnerability
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.eclipse.jgit:org.eclipse.jgit Maven |
|
|
| mercurial PyPI |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| org.eclipse.jgit:org.eclipse.jgit Maven |
|
|
| mercurial PyPI |
|
|
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.
From the CVE record · mitre
Affected Git, Mercurial, Xcode, mine, libgit2, Egit, and JGit versions improperly handle crafted .git/config paths. A remote Git server can use a crafted repository tree to execute arbitrary commands when it is processed on Windows or OS X with a case-insensitive filesystem.
Engineers running the affected Git versions, Mercurial before 3.2.3, Xcode before 6.2 beta 3, mine or Egit before 08-12-2014, libgit2 through 0.21.2, JGit before 08-12-2014, Maven org.eclipse.jgit:org.eclipse.jgit before 3.5.3, or PyPI mercurial before 3.2.3 should check their installations.