Commit f9ade314 by Carlos Martín Nieto Committed by Edward Thomson

CHANGELOG: mention CVE-2018-11235 is covered by v0.27.1

parent df53ce32
...@@ -2,14 +2,19 @@ v0.27.1 ...@@ -2,14 +2,19 @@ v0.27.1
--------- ---------
This is a security release fixing insufficient validation of submodule names This is a security release fixing insufficient validation of submodule names
(CVE-2018-11235, reported by Etienne Stalmans). (CVE-2018-11235, reported by Etienne Stalmans) and disallows `.gitmodules` files
as symlinks.
While submodule names come from the untrusted ".gitmodules" file, we blindly While submodule names come from the untrusted ".gitmodules" file, we blindly
append the name to "$GIT_DIR/modules" to construct the final path of the append the name to "$GIT_DIR/modules" to construct the final path of the
submodule repository. In case the name contains e.g. "../", an adversary would submodule repository. In case the name contains e.g. "../", an adversary would
be able to escape your repository and write data at arbitrary paths. In be able to escape your repository and write data at arbitrary paths. In
accordance with git, we now enforce some rules for submodule names which will accordance with git, we now enforce some rules for submodule names which will
cause libgit2 to ignore these melicious names. cause libgit2 to ignore these malicious names.
Adding a symlink as `.gitmodules` into the index from the workdir or checking
out such files is not allowed as this can make a Git implementation write
outside of the repository and bypass the `fsck` checks for CVE-2018-11235.
libgit2 is not susceptible to CVE-2018-11233. libgit2 is not susceptible to CVE-2018-11233.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment