CVE-2018-11233

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, code to sanity-check pathnames on NTFS can result in reading out-of-bounds memory.

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, code to sanity-check pathnames on NTFS can result in reading out-of-bounds memory.

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, code to sanity-check pathnames on NTFS can result in reading out-of-bounds memory.

It was possible to trick the code that sanity-checks paths on NTFS into reading random piece of memory (CVE-2018-11233).

Submodule "names" come from the untrusted .gitmodules file, but we blindly append them to $GIT_DIR/modules to create our on-disk repo paths. This means you can do bad things by putting "../" into the name. We now enforce some rules for submodule names which will cause Git to ignore these malicious names (CVE-2018-11235).

This update for git fixes the following issues:

Security issues fixed:

• CVE-2020-11008: Specially crafted URLs may have tricked the credentials helper to providing credential information that is not appropriate for the protocol in use and host being contacted (bsc#1169936)

git was updated to 2.26.1 (bsc#1169786, jsc#ECO-1628, bsc#1149792)

• Fix git-daemon not starting after conversion from sysvinit to systemd service (bsc#1169605).

• CVE-2020-5260: Specially crafted URLs with newline characters could have been used to make the Git client to send credential information for a wrong host to the attacker's site bsc#1168930

git 2.26.0 (bsc#1167890, jsc#SLE-11608):

• 'git rebase' now uses a different backend that is based on the 'merge' machinery by default. The 'rebase.backend' configuration variable reverts to old behaviour when set to 'apply'
• Improved handling of sparse checkouts
• Improvements to many commands and internal features

git 2.25.2:

• bug fixes to various subcommands in specific operations

git 2.25.1:

• 'git commit' now honors advise.statusHints
• various updates, bug fixes and documentation updates

git 2.25.0

• The branch description ('git branch --edit-description') has been used to fill the body of the cover letters by the format-patch command; this has been enhanced so that the subject can also be filled.
• A few commands learned to take the pathspec from the standard input or a named file, instead of taking it as the command line arguments, with the '--pathspec-from-file' option.
• Test updates to prepare for SHA-2 transition continues.
• Redo 'git name-rev' to avoid recursive calls.
• When all files from some subdirectory were renamed to the root directory, the directory rename heuristics would fail to detect that as a rename/merge of the subdirectory to the root directory, which has been corrected.
• HTTP transport had possible allocator/deallocator mismatch, which has been corrected.

git 2.24.1:

• CVE-2019-1348: The --export-marks option of fast-import is exposed also via the in-stream command feature export-marks=... and it allows overwriting arbitrary paths (bsc#1158785)
• CVE-2019-1349: on Windows, when submodules are cloned recursively, under certain circumstances Git could be fooled into using the same Git directory twice (bsc#1158787)
• CVE-2019-1350: Incorrect quoting of command-line arguments allowed remote code execution during a recursive clone in conjunction with SSH URLs (bsc#1158788)
• CVE-2019-1351: on Windows mistakes drive letters outside of the US-English alphabet as relative paths (bsc#1158789)
• CVE-2019-1352: on Windows was unaware of NTFS Alternate Data Streams (bsc#1158790)
• CVE-2019-1353: when run in the Windows Subsystem for Linux while accessing a working directory on a regular Windows drive, none of the NTFS protections were active (bsc#1158791)
• CVE-2019-1354: on Windows refuses to write tracked files with filenames that contain backslashes (bsc#1158792)
• CVE-2019-1387: Recursive clones vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones (bsc#1158793)
• CVE-2019-19604: a recursive clone followed by a submodule update could execute code contained within the repository without the user explicitly having asked for that (bsc#1158795)

git 2.24.0

• The command line parser learned '--end-of-options' notation.
• A mechanism to affect the default setting for a (related) group of configuration variables is introduced.
• 'git fetch' learned '--set-upstream' option to help those who first clone from their private fork they intend to push to, add the true upstream via 'git remote add' and then 'git fetch' from it.
• fixes and improvements to UI, workflow and features, bash completion fixes

git 2.23.0:

• The '--base' option of 'format-patch' computed the patch-ids for prerequisite patches in an unstable…

These are all security issues fixed in the git-2.33.0-1.3 package on the GA media of openSUSE Tumbleweed.

This update for git fixes several issues.

These security issues were fixed:

• CVE-2018-11233: Path sanity-checks on NTFS allowed attackers to read arbitrary memory (bsc#1095218)
• CVE-2018-11235: Arbitrary code execution when recursively cloning a malicious repository (bsc#1095219)

This update for git fixes several issues.

These security issues were fixed:

• CVE-2018-11233: Path sanity-checks on NTFS allowed attackers to read arbitrary memory (bsc#1095218)
• CVE-2018-11235: Arbitrary code execution when recursively cloning a malicious repository (bsc#1095219)

This update for git to version 2.16.4 fixes several issues.

These security issues were fixed:

• CVE-2018-11233: Path sanity-checks on NTFS allowed attackers to read arbitrary memory (bsc#1095218)
• CVE-2018-11235: Arbitrary code execution when recursively cloning a malicious repository (bsc#1095219)

This update for git fixes the following issues:

Security issues fixed:

• CVE-2020-11008: Specially crafted URLs may have tricked the credentials helper to providing credential information that is not appropriate for the protocol in use and host being contacted (bsc#1169936)

git was updated to 2.26.1 (bsc#1169786, jsc#ECO-1628, bsc#1149792)

• Fix git-daemon not starting after conversion from sysvinit to systemd service (bsc#1169605).

• CVE-2020-5260: Specially crafted URLs with newline characters could have been used to make the Git client to send credential information for a wrong host to the attacker's site bsc#1168930

git 2.26.0 (bsc#1167890, jsc#SLE-11608):

• 'git rebase' now uses a different backend that is based on the 'merge' machinery by default. The 'rebase.backend' configuration variable reverts to old behaviour when set to 'apply'
• Improved handling of sparse checkouts
• Improvements to many commands and internal features

git 2.25.2:

• bug fixes to various subcommands in specific operations

git 2.25.1:

• 'git commit' now honors advise.statusHints
• various updates, bug fixes and documentation updates

git 2.25.0

• The branch description ('git branch --edit-description') has been used to fill the body of the cover letters by the format-patch command; this has been enhanced so that the subject can also be filled.
• A few commands learned to take the pathspec from the standard input or a named file, instead of taking it as the command line arguments, with the '--pathspec-from-file' option.
• Test updates to prepare for SHA-2 transition continues.
• Redo 'git name-rev' to avoid recursive calls.
• When all files from some subdirectory were renamed to the root directory, the directory rename heuristics would fail to detect that as a rename/merge of the subdirectory to the root directory, which has been corrected.
• HTTP transport had possible allocator/deallocator mismatch, which has been corrected.

git 2.24.1:

• CVE-2019-1348: The --export-marks option of fast-import is exposed also via the in-stream command feature export-marks=... and it allows overwriting arbitrary paths (bsc#1158785)
• CVE-2019-1349: on Windows, when submodules are cloned recursively, under certain circumstances Git could be fooled into using the same Git directory twice (bsc#1158787)
• CVE-2019-1350: Incorrect quoting of command-line arguments allowed remote code execution during a recursive clone in conjunction with SSH URLs (bsc#1158788)
• CVE-2019-1351: on Windows mistakes drive letters outside of the US-English alphabet as relative paths (bsc#1158789)
• CVE-2019-1352: on Windows was unaware of NTFS Alternate Data Streams (bsc#1158790)
• CVE-2019-1353: when run in the Windows Subsystem for Linux while accessing a working directory on a regular Windows drive, none of the NTFS protections were active (bsc#1158791)
• CVE-2019-1354: on Windows refuses to write tracked files with filenames that contain backslashes (bsc#1158792)
• CVE-2019-1387: Recursive clones vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones (bsc#1158793)
• CVE-2019-19604: a recursive clone followed by a submodule update could execute code contained within the repository without the user explicitly having asked for that (bsc#1158795)

git 2.24.0

• The command line parser learned '--end-of-options' notation.
• A mechanism to affect the default setting for a (related) group of configuration variables is introduced.
• 'git fetch' learned '--set-upstream' option to help those who first clone from their private fork they intend to push to, add the true upstream via 'git remote add' and then 'git fetch' from it.
• fixes and improvements to UI, workflow and features, bash completion fixes

git 2.23.0:

• The '--base' option of 'format-patch' computed the patch-ids for prerequisite patches in an unstable…

Etienne Stalmans discovered that git did not properly validate git submodules files. A remote attacker could possibly use this to craft a git repo that causes arbitrary code execution when "git clone --recurse-submodules" is used. (CVE-2018-11235)

It was discovered that an integer overflow existed in git's pathname consistency checking code when used on NTFS filesystems. An attacker could use this to cause a denial of service or expose sensitive information. (CVE-2018-11233)