JGit Improper Input Validation vulnerability
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; libgit2; Egit; and JGit 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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2014-9390US | critical9.8 | Exploit | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- http://article.gmane.org/gmane.linux.kernel/1853266WEB
- http://git-blame.blogspot.com/2014/12/git-1856-195-205-214-and-221-and.htmlWEB
- http://mercurial.selenic.com/wiki/WhatsNewWEB
- http://securitytracker.com/id?1031404WEB
- http://support.apple.com/kb/HT204147WEB
- https://github.com/blog/1938-git-client-vulnerability-announcedWEB
- https://github.com/libgit2/libgit2/commit/928429c5c96a701bcbcafacb2421a82602b36915WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/mercurial/PYSEC-2020-217.yamlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan