An update for jgit is now available for openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP3,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS,openEuler-22.03-LTS-SP1 and openEuler-22.03-LTS-SP2 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2023-1995 Final 1.0 1.0 2023-12-29 Initial 2023-12-29 2023-12-29 openEuler SA Tool V1.0 2023-12-29 jgit security update An update for jgit is now available for openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP3,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS,openEuler-22.03-LTS-SP1 and openEuler-22.03-LTS-SP2. A pure Java implementation of the Git version control system and command line interface. Security Fix(es): Arbitrary File Overwrite in Eclipse JGit <= 6.6.0 In Eclipse JGit, all versions <= 6.6.0.202305301015-r, a symbolic link present in a specially crafted git repository can be used to write a file to locations outside the working tree when this repository is cloned with JGit to a case-insensitive filesystem, or when a checkout from a clone of such a repository is performed on a case-insensitive filesystem. This can happen on checkout (DirCacheCheckout), merge (ResolveMerger via its WorkingTreeUpdater), pull (PullCommand using merge), and when applying a patch (PatchApplier). This can be exploited for remote code execution (RCE), for instance if the file written outside the working tree is a git filter that gets executed on a subsequent git command. The issue occurs only on case-insensitive filesystems, like the default filesystems on Windows and macOS. The user performing the clone or checkout must have the rights to create symbolic links for the problem to occur, and symbolic links must be enabled in the git configuration. Setting git configuration option core.symlinks = false before checking out avoids the problem. The issue was fixed in Eclipse JGit version 6.6.1.202309021850-r and 6.7.0.202309050840-r, available via Maven Central https://repo1.maven.org/maven2/org/eclipse/jgit/  and repo.eclipse.org https://repo.eclipse.org/content/repositories/jgit-releases/ . The JGit maintainers would like to thank RyotaK for finding and reporting this issue. (CVE-2023-4759) An update for jgit is now available for openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP3,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS,openEuler-22.03-LTS-SP1 and openEuler-22.03-LTS-SP2. openEuler Security has rated this update as having a security impact of high. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. High jgit https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1995 https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-4759 https://nvd.nist.gov/vuln/detail/CVE-2023-4759 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP3 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS openEuler-22.03-LTS-SP1 openEuler-22.03-LTS-SP2 jgit-javadoc-5.11.0-3.oe1.noarch.rpm jgit-5.11.0-3.oe1.noarch.rpm jgit-javadoc-5.11.0-3.oe1.noarch.rpm jgit-5.11.0-3.oe1.noarch.rpm jgit-javadoc-5.11.0-3.oe2003sp4.noarch.rpm jgit-5.11.0-3.oe2003sp4.noarch.rpm jgit-javadoc-5.11.0-3.oe2203.noarch.rpm jgit-5.11.0-3.oe2203.noarch.rpm jgit-javadoc-5.11.0-3.oe2203sp1.noarch.rpm jgit-5.11.0-3.oe2203sp1.noarch.rpm jgit-javadoc-5.11.0-3.oe2203sp2.noarch.rpm jgit-5.11.0-3.oe2203sp2.noarch.rpm jgit-5.11.0-3.oe1.src.rpm jgit-5.11.0-3.oe1.src.rpm jgit-5.11.0-3.oe2003sp4.src.rpm jgit-5.11.0-3.oe2203.src.rpm jgit-5.11.0-3.oe2203sp1.src.rpm jgit-5.11.0-3.oe2203sp2.src.rpm Arbitrary File Overwrite in Eclipse JGit <= 6.6.0In Eclipse JGit, all versions <= 6.6.0.202305301015-r, a symbolic link present in a specially crafted git repository can be used to write a file to locations outside the working tree when this repository is cloned with JGit to a case-insensitive filesystem, or when a checkout from a clone of such a repository is performed on a case-insensitive filesystem.This can happen on checkout (DirCacheCheckout), merge (ResolveMerger via its WorkingTreeUpdater), pull (PullCommand using merge), and when applying a patch (PatchApplier). This can be exploited for remote code execution (RCE), for instance if the file written outside the working tree is a git filter that gets executed on a subsequent git command.The issue occurs only on case-insensitive filesystems, like the default filesystems on Windows and macOS. The user performing the clone or checkout must have the rights to create symbolic links for the problem to occur, and symbolic links must be enabled in the git configuration.Setting git configuration option core.symlinks = false before checking out avoids the problem.The issue was fixed in Eclipse JGit version 6.6.1.202309021850-r and 6.7.0.202309050840-r, available via Maven Central https://repo1.maven.org/maven2/org/eclipse/jgit/  and repo.eclipse.org https://repo.eclipse.org/content/repositories/jgit-releases/ .The JGit maintainers would like to thank RyotaK for finding and reporting this issue. 2023-12-29 CVE-2023-4759 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP3 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS openEuler-22.03-LTS-SP1 openEuler-22.03-LTS-SP2 High 8.8 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H jgit security update 2023-12-29 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1995