CVE-2023-4759: Arbitrary File Overwrite in Eclipse JGit
Summary
CVE-2023-4759: Arbitrary File Overwrite in Eclipse JGit. Affects org.eclipse.jgit:org.eclipse.jgit across 2 version ranges.
< 5.13.3.202401111512-r
>= 6.0.0.202111291000-r, < 6.6.1.202309021850-r
Fixed in 5.13.3.202401111512-r or 6.6.1.202309021850-r, depending on the release line you run. How to fix ↓
Also tracked for
- jgit · Debian:11
The same CVE-2023-4759 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Eclipse JGit is an open-source Java implementation of the Git version control system. It provides functionality for managing repositories, performing operations like cloning, merging, and applying patches. JGit is widely used in various software development projects. However, versions up to 6.6.0.202305301015-r are vulnerable to an arbitrary file overwrite issue.
Vulnerability Detail
The vulnerability in Eclipse JGit allows an attacker to write a file to locations outside the working tree when cloning a specially crafted git repository on a case-insensitive filesystem. This can also occur during a checkout from a clone of such a repository. The issue arises due to the presence of a symbolic link in the repository. On case-insensitive filesystems like Windows and macOS, the attacker can exploit this to achieve remote code execution (RCE) if the written file is a git filter executed in subsequent git commands. The vulnerability affects versions <= 6.6.0.202305301015-r.
How To Fix
Latest published version: 7.8.0.202609011348-r as of 22 Oct 2026
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 5.13.3.202401111512-r5.13.3.202401111512-r -
>= 6.0.0.202111291000-r, < 6.6.1.202309021850-r6.6.1.202309021850-r
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary workaround, users can disable symbolic links in the git configuration by setting the option 'core.symlinks' to 'false' before performing a checkout. This can be done using the following command:
git config core.symlinks false
Conclusion
The arbitrary file overwrite vulnerability in Eclipse JGit can be mitigated by updating to the fixed versions or disabling symbolic links in the git configuration. It is recommended to apply the necessary updates to ensure the security of your software. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.eclipse.jgit:org.eclipse.jgit →
FAQ
The vulnerability allows an attacker to write files outside the working tree, potentially leading to remote code execution (RCE) if the written file is a git filter executed in subsequent git commands.
The vulnerability affects all versions of Eclipse JGit up to and including 6.6.0.202305301015-r.
No, the vulnerability only affects case-insensitive filesystems like Windows and macOS.
Yes, the user performing the clone or checkout must have the rights to create symbolic links for the vulnerability to occur.
Yes, updating Eclipse JGit to version 6.6.1.202309021850-r or 6.7.0.202309050840-r resolves the vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for org.eclipse.jgit:org.eclipse.jgit.
