Errors in handling case-sensitive directories allow for remote code execution on pull
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
git (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Tyler Hicks | ||
Trusty |
Fix Released
|
Medium
|
Tyler Hicks | ||
Utopic |
Fix Released
|
Medium
|
Tyler Hicks | ||
Vivid |
Fix Released
|
Medium
|
Unassigned | ||
jgit (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Confirmed
|
Undecided
|
Unassigned | ||
Utopic |
Invalid
|
Undecided
|
Unassigned | ||
Vivid |
Invalid
|
Undecided
|
Unassigned | ||
libgit2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Confirmed
|
Undecided
|
Unassigned | ||
Utopic |
Invalid
|
Undecided
|
Unassigned | ||
Vivid |
Invalid
|
Undecided
|
Unassigned | ||
mercurial (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Jamie Strandboge | ||
Trusty |
Fix Released
|
Medium
|
Jamie Strandboge | ||
Utopic |
Fix Released
|
Medium
|
Jamie Strandboge | ||
Vivid |
Fix Released
|
Medium
|
Unassigned |
Bug Description
From the upstream announcement[1]:
This is a security-fix for CVE-2014-9390, which affects users on
Windows and Mac OS X but not typical UNIX users. A set of new
releases for older maintenance tracks (v1.8.5.6, v1.9.5, v2.0.5, and
v2.1.4) are published at the same time and they contain the same fix.
Various implementations and ports, including Git for Windows, Git OS
X installer, JGit & EGit, libgit2 (and Visual Studio which uses it)
have been updated at the same time.
Even though the issue may not affect Linux users, if you are a
hosting service whose users may fetch from your service to Windows
or Mac OS X machines, you are strongly encouraged to update to
protect such users who use existing versions of Git.
This issue also affects hg[2].
[1]: http://
[2]: http://
Changed in git (Ubuntu): | |
importance: | Undecided → High |
information type: | Public → Public Security |
Changed in mercurial (Ubuntu): | |
importance: | Undecided → High |
Changed in git (Ubuntu): | |
status: | New → Confirmed |
Changed in mercurial (Ubuntu): | |
status: | New → Confirmed |
no longer affects: | libgit2 (Ubuntu Precise) |
Changed in jgit (Ubuntu Trusty): | |
status: | New → Confirmed |
Changed in jgit (Ubuntu Utopic): | |
status: | New → Confirmed |
Changed in jgit (Ubuntu Vivid): | |
status: | New → Confirmed |
Changed in libgit2 (Ubuntu Utopic): | |
status: | Confirmed → Invalid |
Changed in libgit2 (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in jgit (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in jgit (Ubuntu Utopic): | |
status: | Confirmed → Invalid |
Changed in jgit (Ubuntu Vivid): | |
status: | Confirmed → Invalid |
Changed in libgit2 (Ubuntu Vivid): | |
status: | Confirmed → Invalid |
FYI, mercurial is in universe and is therefore community maintained. I took a look at it and have prepared packages in https:/ /launchpad. net/~ubuntu- security- proposed/ +archive/ ubuntu/ ppa/+packages. If someone could test them and verify they are ok, I can push them out as a security update.