This update for git fixes the following issues :

  - On case-insensitive filesystems, with support for     symbolic links, if Git is configured globally to apply     delay-capable clean/smudge filters (such as Git LFS),     Git could be fooled into running remote code during a     clone. (bsc#1183026, CVE-2021-21300)

This update was imported from the SUSE:SLE-15:Update update project.

An update of the git package has been released.

According to the version of the git packages installed, the EulerOS installation on the remote host is affected by the following vulnerability :

  - Git is an open-source distributed revision control     system. In affected versions of Git a specially crafted     repository that contains symbolic links as well as     files using a clean/smudge filter such as Git LFS,may     cause just-checked out script to be executed while     cloning onto a case-insensitive file system such as     NTFS,HFS+ or APFS (i.e. the default file systems on     Windows and macOS). Note that clean/smudge filters have     to be configured for that. Git for Windows configures     Git LFS by default,and is therefore vulnerable. The     problem has been patched in the versions published on     Tuesday,March 9th,2021. As a workaound,if symbolic link     support is disabled in Git (e.g. via `git config
    --global core.symlinks false`),the described attack     won't work. Likewise,if no clean/smudge filters such as     Git LFS are configured globally (i.e. _before_     cloning),the attack is foiled. As always,it is best to     avoid cloning repositories from untrusted     sources.(CVE-2021-21300)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote host is affected by the vulnerability described in GLSA-202104-01 (Git: User-assisted execution of arbitrary code)

    It was discovered that Git could be fooled into running remote code       during a clone on case-insensitive file systems with support for symbolic       links, if Git is configured globally to apply delay-capable clean/smudge       filters (such as Git LFS).
  Impact :

    A remote attacker could entice a user to clone a specially crafted       repository, possibly resulting in the remote execution of arbitrary code       with the privileges of the user running the application.
  Workaround :

    There is no known workaround at this time.

This update for git fixes the following issues :

On case-insensitive filesystems, with support for symbolic links, if Git is configured globally to apply delay-capable clean/smudge filters (such as Git LFS), Git could be fooled into running remote code during a clone. (bsc#1183026, CVE-2021-21300)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Ubuntu 16.04 LTS / 18.04 LTS / 20.04 LTS host has packages installed that are affected by a vulnerability as referenced in the USN-4761-1 advisory.

    Matheus Tavares discovered that Git incorrectly handled delay-capable clean/smudge filters when being used     on case-insensitive filesystems. A remote attacker could possibly use this issue to execute arbitrary     code.

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SUSE15 host has packages installed that are affected by a vulnerability as referenced in the openSUSE-SU-2021:2555-1 advisory.

  - Git is an open-source distributed revision control system. In affected versions of Git a specially crafted     repository that contains symbolic links as well as files using a clean/smudge filter such as Git LFS, may     cause just-checked out script to be executed while cloning onto a case-insensitive file system such as     NTFS, HFS+ or APFS (i.e. the default file systems on Windows and macOS). Note that clean/smudge filters     have to be configured for that. Git for Windows configures Git LFS by default, and is therefore     vulnerable. The problem has been patched in the versions published on Tuesday, March 9th, 2021. As a     workaound, if symbolic link support is disabled in Git (e.g. via `git config --global core.symlinks     false`), the described attack won't work. Likewise, if no clean/smudge filters such as Git LFS are     configured globally (i.e. _before_ cloning), the attack is foiled. As always, it is best to avoid cloning     repositories from untrusted sources. The earliest impacted version is 2.14.2. The fix versions are:
    2.30.1, 2.29.3, 2.28.1, 2.27.1, 2.26.3, 2.25.5, 2.24.4, 2.23.4, 2.22.5, 2.21.4, 2.20.5, 2.19.6, 2.18.5,     2.17.62.17.6. (CVE-2021-21300)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLED15 / SLES15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2021:2555-1 advisory.

    Update from version 2.26.2 to version 2.31.1 (jsc#SLE-18152)

    Security fixes:

    - CVE-2021-21300: On case-insensitive file systems with support for symbolic links, if Git is configured     globally       to apply delay-capable clean/smudge filters (such as Git LFS), Git could run remote code during a clone.
    (bsc#1183026)

    Non security changes:

    - Add `sysusers` file to create `git-daemon` user.
    - Remove `perl-base` and `openssh-server` dependency on `git-core`and provide a `perl-Git` package.
    (jsc#SLE-17838)
    - `fsmonitor` bug fixes
    - Fix `git bisect` to take an annotated tag as a good/bad endpoint
    - Fix a corner case in `git mv` on case insensitive systems
    - Require only `openssh-clients` where possible (like Tumbleweed or SUSE Linux Enterprise >= 15 SP3).
    (bsc#1183580)
    - Drop `rsync` requirement, not necessary anymore.
    - Use of `pack-redundant` command is discouraged and will trigger a warning. The replacement is `repack
    -d`.
    - The `--format=%(trailers)` mechanism gets enhanced to make it easier to design output for machine     consumption.
    - No longer give message to choose between rebase or merge upon pull if the history `fast-forwards`.
    - The configuration variable `core.abbrev` can be set to `no` to force no abbreviation regardless of the     hash algorithm
    - `git rev-parse` can be explicitly told to give output as absolute or relative path with the       `--path-format=(absolute|relative)` option.
    - Bash completion update to make it easier for end-users to add completion for their custom `git`     subcommands.
    - `git maintenance` learned to drive scheduled maintenance on platforms whose native scheduling methods     are not 'cron'.
    - After expiring a reflog and making a single commit, the reflog for the branch would record a single     entry that       knows both `@{0}` and `@{1}`, but we failed to answer 'what commit were we on?', i.e. `@{1}`
    - `git bundle` learns `--stdin` option to read its refs from the standard input.
      Also, it now does not lose refs when they point at the same object.
    - `git log` learned a new `--diff-merges=<how>` option.
    - `git ls-files` can and does show multiple entries when the index is unmerged, which is a source for     confusion       unless `-s/-u` option is in use.  A new option `--deduplicate` has been introduced.
    - `git worktree list` now annotates worktrees as prunable, shows locked and prunable attributes       in `--porcelain mode`, and gained a `--verbose` option.
    - `git clone` tries to locally check out the branch pointed at by HEAD of the remote repository after it       is done, but the protocol did not convey the information necessary to do so when copying an empty     repository.
      The protocol v2 learned how to do so.
    - There are other ways than `..` for a single token to denote a `commit range', namely `<rev>^!`        and `<rev>^-<n>`, but `git range-diff` did not understand them.
    - The `git range-diff` command learned `--(left|right)-only` option to show only one side of the compared     range.
    - `git mergetool` feeds three versions (base, local and remote) of a conflicted path unmodified.
      The command learned to optionally prepare these files with unconflicted parts already resolved.
    - The `.mailmap` is documented to be read only from the root level of a working tree, but a stray file       in a bare repository also was read by accident, which has been corrected.
    - `git maintenance` tool learned a new `pack-refs` maintenance task.
    - Improved error message given when a configuration variable that is expected to have a boolean value.
    - Signed commits and tags now allow verification of objects, whose two object names       (one in SHA-1, the other in SHA-256) are both signed.
    - `git rev-list` command learned `--disk-usage` option.
    - `git diff`, `git log` `--{skip,rotate}-to=<path>` allows the user to discard diff output for early       paths or move them to the end of the output.
    - `git difftool` learned `--skip-to=<path>` option to restart an interrupted session from an arbitrary     path.
    - `git grep` has been tweaked to be limited to the sparse checkout paths.
    - `git rebase --[no-]fork-point` gained a configuration variable `rebase.forkPoint` so that users do not     have       to keep specifying a non-default setting.
    - `git stash` did not work well in a sparsely checked out working tree.
    - Newline characters in the host and path part of `git://` URL are now forbidden.
    - `Userdiff` updates for PHP, Rust, CSS
    - Avoid administrator error leading to data loss with `git push --force-with-lease[=<ref>]` by       introducing `--force-if-includes`
    - only pull `asciidoctor` for the default ruby version
    - The `--committer-date-is-author-date` option of `rebase` and `am` subcommands lost the e-mail address by       mistake in 2.29
    - The transport protocol v2 has become the default again
    - `git worktree` gained a `repair` subcommand, `git init --separate-git-dir` no longer corrupts     administrative data       related to linked worktrees
    - `git maintenance` introduced for repository maintenance tasks
    - `fetch.writeCommitGraph` is deemed to be still a bit too risky and is no longer part of the       `feature.experimental` set.
    - The commands in the `diff` family honors the `diff.relative` configuration variable.
    - `git diff-files` has been taught to say paths that are marked as `intent-to-add` are new files,       not modified from an empty blob.
    - `git gui` now allows opening work trees from the start-up dialog.
    - `git bugreport` reports what shell is in use.
    - Some repositories have commits that record wrong committer timezone; `git fast-import` has an option to     pass       these timestamps intact to allow recreating existing repositories as-is.
    - `git describe` will always use the `long` version when giving its output based misplaced tags
    - `git pull` issues a warning message until the `pull.rebase` configuration variable is explicitly given

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

According to the version of the git packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerability :

  - Git is an open-source distributed revision control     system. In affected versions of Git a specially crafted     repository that contains symbolic links as well as     files using a clean/smudge filter such as Git LFS, may     cause just-checked out script to be executed while     cloning onto a case-insensitive file system such as     NTFS, HFS+ or APFS (i.e. the default file systems on     Windows and macOS). Note that clean/smudge filters have     to be configured for that. Git for Windows configures     Git LFS by default, and is therefore vulnerable. The     problem has been patched in the versions published on     Tuesday, March 9th, 2021. As a workaound, if symbolic     link support is disabled in Git (e.g. via `git config
    --global core.symlinks false`), the described attack     won't work. Likewise, if no clean/smudge filters such     as Git LFS are configured globally (i.e. _before_     cloning), the attack is foiled. As always, it is best     to avoid cloning repositories from untrusted sources.
    The earliest impacted version is 2.14.2. The fix     versions are: 2.30.1, 2.29.3, 2.28.1, 2.27.1, 2.26.3,     2.25.5, 2.24.4, 2.23.4, 2.22.5, 2.21.4, 2.20.5, 2.19.6,     2.18.5, 2.17.62.17.6.(CVE-2021-21300)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

New git packages are available for Slackware 14.0, 14.1, 14.2, and
-current to fix a security issue.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
147799	openSUSE Security Update : git (openSUSE-2021-405)	Nessus	SuSE Local Security Checks	2021/3/15	2022/1/26	high
147824	Photon OS 2.0: Git PHSA-2021-2.0-0327	Nessus	PhotonOS Local Security Checks	2021/3/16	2024/7/22	high
149563	EulerOS 2.0 SP8 : git (EulerOS-SA-2021-1870)	Nessus	Huawei Local Security Checks	2021/5/18	2024/1/1	high
149221	GLSA-202104-01 : Git: User-assisted execution of arbitrary code	Nessus	Gentoo Local Security Checks	2021/5/3	2024/1/12	high
147564	SUSE SLED15 / SLES15 Security Update : git (SUSE-SU-2021:0757-1)	Nessus	SuSE Local Security Checks	2021/3/10	2022/1/26	high
147821	Photon OS 3.0: Git PHSA-2021-3.0-0207	Nessus	PhotonOS Local Security Checks	2021/3/16	2025/8/22	high
148010	Ubuntu 16.04 LTS / 18.04 LTS / 20.04 LTS : Git vulnerability (USN-4761-1)	Nessus	Ubuntu Local Security Checks	2021/3/23	2024/8/28	high
152154	openSUSE 15 Security Update : git (openSUSE-SU-2021:2555-1)	Nessus	SuSE Local Security Checks	2021/7/30	2022/1/20	high
152157	SUSE SLED15: git / git-arch / git-core / git-cvs / git-daemon / git-doc / etc (SUSE-SU-2021:2555-1)	Nessus	SuSE Local Security Checks	2021/7/30	2026/6/25	high
147436	SUSE SLES12 Security Update : git (SUSE-SU-2021:0756-1)	Nessus	SuSE Local Security Checks	2021/3/10	2022/1/26	high
151242	EulerOS Virtualization 3.0.6.6 : git (EulerOS-SA-2021-2033)	Nessus	Huawei Local Security Checks	2021/7/1	2023/12/11	high
147737	Slackware 14.0 / 14.1 / 14.2 / current : git (SSA:2021-070-01)	Nessus	Slackware Local Security Checks	2021/3/12	2022/1/26	high
252274	Photon OS 5.0: Git PHSA-2025-5.0-0590	Nessus	PhotonOS Local Security Checks	2025/8/19	2025/8/23	critical

检测

插件搜索

high

high

high

high

high

high

high

high

high

high

high

high

critical