Summary
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 way, which has been updated
to compute in a way that is compatible with 'git patch-id
--stable'.
* The 'git log' command by default behaves as if the --mailmap
option was given.
* fixes and improvements to UI, workflow and features
git 2.22.1
* A relative pathname given to 'git init --template=<path> <repo>'
ought to be relative to the directory 'git init' gets invoked in,
but it instead was made relative to the repository, which has been
corrected.
* 'git worktree add' used to fail when another worktree connected to
the same repository was corrupt, which has been corrected.
* 'git am -i --resolved' segfaulted after trying to see a commit as
if it were a tree, which has been corrected.
* 'git merge --squash' is designed to update the working tree and the
index without creating the commit, and this cannot be countermanded
by adding the '--commit' option; the command now refuses to work
when both options are given.
* Update to Unicode 12.1 width table.
* 'git request-pull' learned to warn when the ref we ask them to pull
from in the local repository and in the published repository are
different.
* 'git fetch' into a lazy clone forgot to fetch base objects that are
necessary to complete delta in a thin packfile, which has been
corrected.
* The URL decoding code has been updated to avoid going past the end
of the string while parsing %-<hex>-<hex> sequence.
* 'git clean' silently skipped a path when it cannot lstat() it; now
it gives a warning.
* 'git rm' to resolve a conflicted path leaked an internal message
'needs merge' before actually removing the path, which was
confusing. This has been corrected.
* Many more bugfixes and code cleanups.
- removal of SuSEfirewall2 service, since SuSEfirewall2 has been replaced by
firewalld.
- partial fix for git instaweb giving 500 error (bsc#1112230)
git 2.22.0
* The filter specification '--filter=sparse:path=<path>' used to
create a lazy/partial clone has been removed. Using a blob
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 15.1 | git | 2.26.1-lp151.4.9.1 |
Vulnerabilities 15
-
Critical 9.3
malicious URLs may cause Git to present stored credentials to the wrong server
Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external "credential helper" programs to store and retrieve passwords or other credentials from secure stor…
-
Medium 4.0
Malicious URLs can still cause Git to send a stored credential to the wrong server
Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. This bug is similar to CVE-2020-5260(GHSA-qm7j-c969-7j4q). The fix for that bug still left the door open for an expl…
-
Unscored —
Git through 2.14.2 mishandles layers of tree objects, which allows remote attackers to cause a denial of service (memor…
-
Unscored —
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 …
-
Unscored —
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, remot…
-
Unscored —
Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x b…
-
Unscored —
An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15…
-
Unscored —CVE-2019-1349 EPSS 36%
A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual…
-
Unscored —CVE-2019-1350 EPSS 27%
A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual…
-
Unscored —
A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual…
-
Unscored —CVE-2019-1352 EPSS 26%
A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual…
-
Unscored —
An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15…
-
Unscored —CVE-2019-1354 EPSS 24%
A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual…
-
Unscored —
An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15…
-
Unscored —
Arbitrary command execution is possible in Git before 2.20.2, 2.21.x before 2.21.1, 2.22.x before 2.22.2, 2.23.x before…
References
-
report
https://bugzilla.suse.com/1063412
-
report
https://bugzilla.suse.com/1095218
-
report
https://bugzilla.suse.com/1095219
-
report
https://bugzilla.suse.com/1110949
-
report
https://bugzilla.suse.com/1112230
-
report
https://bugzilla.suse.com/1114225
-
report
https://bugzilla.suse.com/1132350
-
report
https://bugzilla.suse.com/1149792
-
report
https://bugzilla.suse.com/1156651
-
report
https://bugzilla.suse.com/1158785
-
report
https://bugzilla.suse.com/1158787
-
report
https://bugzilla.suse.com/1158788
-
report
https://bugzilla.suse.com/1158789
-
report
https://bugzilla.suse.com/1158790
-
report
https://bugzilla.suse.com/1158791
-
report
https://bugzilla.suse.com/1158792
-
report
https://bugzilla.suse.com/1158793
-
report
https://bugzilla.suse.com/1158795
-
report
https://bugzilla.suse.com/1167890
-
report
https://bugzilla.suse.com/1168930
-
report
https://bugzilla.suse.com/1169605
-
report
https://bugzilla.suse.com/1169786
-
report
https://bugzilla.suse.com/1169936
-
web
https://www.suse.com/security/cve/CVE-2017-15298
-
web
https://www.suse.com/security/cve/CVE-2018-11233
-
web
https://www.suse.com/security/cve/CVE-2018-11235
-
web
https://www.suse.com/security/cve/CVE-2018-17456
-
web
https://www.suse.com/security/cve/CVE-2019-1348
-
web
https://www.suse.com/security/cve/CVE-2019-1349
-
web
https://www.suse.com/security/cve/CVE-2019-1350
-
web
https://www.suse.com/security/cve/CVE-2019-1351
-
web
https://www.suse.com/security/cve/CVE-2019-1352
-
web
https://www.suse.com/security/cve/CVE-2019-1353
-
web
https://www.suse.com/security/cve/CVE-2019-1354
-
web
https://www.suse.com/security/cve/CVE-2019-1387
-
web
https://www.suse.com/security/cve/CVE-2019-19604
-
web
https://www.suse.com/security/cve/CVE-2020-11008
-
web
https://www.suse.com/security/cve/CVE-2020-5260