Описание
ELSA-2018-1957: git security update (IMPORTANT)
[1.8.3.1-14]
- Backport fix for CVE-2018-1123
- Thanks to Jonathan Nieder jrnieder@gmail.com for backporting to 2.1.x and to Steve Beattie sbeattie@ubuntu.com for backporting to 1.9.1
Обновленные пакеты
Oracle Linux 7
Oracle Linux aarch64
emacs-git
1.8.3.1-14.el7_5
emacs-git-el
1.8.3.1-14.el7_5
git
1.8.3.1-14.el7_5
git-all
1.8.3.1-14.el7_5
git-bzr
1.8.3.1-14.el7_5
git-cvs
1.8.3.1-14.el7_5
git-daemon
1.8.3.1-14.el7_5
git-email
1.8.3.1-14.el7_5
git-gui
1.8.3.1-14.el7_5
git-hg
1.8.3.1-14.el7_5
git-p4
1.8.3.1-14.el7_5
git-svn
1.8.3.1-14.el7_5
gitk
1.8.3.1-14.el7_5
gitweb
1.8.3.1-14.el7_5
perl-Git
1.8.3.1-14.el7_5
perl-Git-SVN
1.8.3.1-14.el7_5
Oracle Linux x86_64
emacs-git
1.8.3.1-14.el7_5
emacs-git-el
1.8.3.1-14.el7_5
git
1.8.3.1-14.el7_5
git-all
1.8.3.1-14.el7_5
git-bzr
1.8.3.1-14.el7_5
git-cvs
1.8.3.1-14.el7_5
git-daemon
1.8.3.1-14.el7_5
git-email
1.8.3.1-14.el7_5
git-gui
1.8.3.1-14.el7_5
git-hg
1.8.3.1-14.el7_5
git-p4
1.8.3.1-14.el7_5
git-svn
1.8.3.1-14.el7_5
gitk
1.8.3.1-14.el7_5
gitweb
1.8.3.1-14.el7_5
perl-Git
1.8.3.1-14.el7_5
perl-Git-SVN
1.8.3.1-14.el7_5
Связанные CVE
Связанные уязвимости
In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur. With a crafted .gitmodules file, a malicious project can execute an arbitrary script on a machine that runs "git clone --recurse-submodules" because submodule "names" are obtained from this file, and then appended to $GIT_DIR/modules, leading to directory traversal with "../" in a name. Finally, post-checkout hooks from a submodule are executed, bypassing the intended design in which hooks are not obtained from a remote server.
In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur. With a crafted .gitmodules file, a malicious project can execute an arbitrary script on a machine that runs "git clone --recurse-submodules" because submodule "names" are obtained from this file, and then appended to $GIT_DIR/modules, leading to directory traversal with "../" in a name. Finally, post-checkout hooks from a submodule are executed, bypassing the intended design in which hooks are not obtained from a remote server.
In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur. With a crafted .gitmodules file, a malicious project can execute an arbitrary script on a machine that runs "git clone --recurse-submodules" because submodule "names" are obtained from this file, and then appended to $GIT_DIR/modules, leading to directory traversal with "../" in a name. Finally, post-checkout hooks from a submodule are executed, bypassing the intended design in which hooks are not obtained from a remote server.
In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16 ...
In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur. With a crafted .gitmodules file, a malicious project can execute an arbitrary script on a machine that runs "git clone --recurse-submodules" because submodule "names" are obtained from this file, and then appended to $GIT_DIR/modules, leading to directory traversal with "../" in a name. Finally, post-checkout hooks from a submodule are executed, bypassing the intended design in which hooks are not obtained from a remote server.