Get a Demo

Let's Patch It!

Book a short call with one our specialists, we'll walk you through how Endor Patches work, and ask you a few questions about your environment (like your primary programming languages and repository management). We'll also send you an email right after you fill out the form, feel free to reply with any questions you have in advance!

CVE

GHSA-3p86-9955-h393

Arbitrary File Overwrite in Eclipse JGit
Back to all
CVE

GHSA-3p86-9955-h393

Arbitrary File Overwrite in Eclipse JGit

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/ . A backport is available in 5.13.3 starting from 5.13.3.202401111512-r.

The JGit maintainers would like to thank RyotaK for finding and reporting this issue.

​

Package Versions Affected

Package Version
patch Availability
org.eclipse.jgit:org.eclipse.jgit 6.6.0.202305301015-r
Available
Unavailable

Automatically patch vulnerabilities without upgrading

Fix Without Upgrading
Detect compatible fix
Apply safe remediation
Fix with a single pull request

CVSS Version

Severity
Base Score
CVSS Version
Score Vector
C
H
U
8.8
-
3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
C
H
U
0
-
3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
C
H
U
8.8
-
3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Related Resources

No items found.

References

https://nvd.nist.gov/vuln/detail/CVE-2023-4759, https://github.com/eclipse-jgit/jgit/issues/30, https://git.eclipse.org/c/jgit/jgit.git, https://git.eclipse.org/c/jgit/jgit.git/commit/?id=9072103f3b3cf64dd12ad2949836ab98f62dabf1, https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/11, https://projects.eclipse.org/projects/technology.jgit/releases/5.13.3, https://projects.eclipse.org/projects/technology.jgit/releases/6.6.1

Severity

8.8

CVSS Score
0
10

Basic Information

Ecosystem
Base CVSS
8.8
EPSS Probability
0.00974%
EPSS Percentile
0.76189%
Introduced Version
1.2.0.201112221803-r,1.3.0.201202151440-r,2.0.0.201206130900-r,2.2.0.201212191850-r,3.0.0.201306101825-r,3.4.0.201405281120-rc2,3.6.0.201412230720-r,4.0.0.201505050340-m2,4.0.0.201505260635-rc2,4.3.0.201604071810-r,4.11.0.201803080745-r,5.0.0.201805151920-m7,4.2.0.201601211800-r,5.6.0.201912101111-r,6.0.0.202111291000-r,5.3.0.201903130848-r,6.3.0.202209071007-r,6.4.0.202211300538-r,6.6.0.202305301015-r
Fix Available
5.13.3.202401111512-r,6.6.1.202309021850-r

Fix Critical Vulnerabilities Instantly

Secure your app without upgrading.
Fix Without Upgrading