GHSA-3p86-9955-h393
First published: Mon Sep 18 2023(Updated: )
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.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| maven/org.eclipse.jgit:org.eclipse.jgit | <5.13.3.202401111512-r | 5.13.3.202401111512-r |
| maven/org.eclipse.jgit:org.eclipse.jgit | >=6.0.0.202111291000-r<=6.6.0.202305301015-r | 6.6.1.202309021850-r |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://nvd.nist.gov/vuln/detail/CVE-2023-4759
- 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/6.6.1
- https://github.com/advisories/GHSA-3p86-9955-h393 (Advisory)
- https://github.com/eclipse-jgit/jgit/issues/30
- https://projects.eclipse.org/projects/technology.jgit/releases/5.13.3
Frequently Asked Questions
What is the severity of GHSA-3p86-9955-h393?
The severity of GHSA-3p86-9955-h393 is high with a severity value of 8.8.
How does the Arbitrary File Overwrite vulnerability in Eclipse JGit <= 6.6.0 work?
In Eclipse JGit <= 6.6.0, 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 file system.
Which versions of Eclipse JGit are affected by the Arbitrary File Overwrite vulnerability?
All versions of Eclipse JGit up to 6.6.0 are affected by the Arbitrary File Overwrite vulnerability.
How can I fix the Arbitrary File Overwrite vulnerability in Eclipse JGit?
To fix the Arbitrary File Overwrite vulnerability in Eclipse JGit, update to version 6.6.1.202309021850-r or later.
Where can I find more information about the Arbitrary File Overwrite vulnerability in Eclipse JGit?
You can find more information about the Arbitrary File Overwrite vulnerability in Eclipse JGit at the following references: [link1], [link2], [link3].
- agent/type
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-3p86-9955-h393
- alias/CVE-2023-4759
- agent/software-canonical-lookup
- agent/severity
- agent/last-modified-date
- agent/weakness
- agent/references
- agent/tags
- agent/softwarecombine
- agent/event
- agent/description
- collector/github-advisory
- package-manager/maven