Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jgit/org.eclipse.jgit/4.5.2.201704071617-r/org.eclipse.jgit-4.5.2.201704071617-r.jar
Directory traversal vulnerability in JCraft JSch before 0.1.54 on Windows, when the mode is ChannelSftp.OVERWRITE, allows remote SFTP servers to write to arbitrary files via a ..\ (dot dot backslash) in a response to a recursive GET command.
Direct dependency fix Resolution (org.eclipse.jgit:org.eclipse.jgit): 4.7.0.201704051617-r
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
CVE-2023-4759
### Vulnerable Library - org.eclipse.jgit-4.5.2.201704071617-r.jar
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jgit/org.eclipse.jgit/4.5.2.201704071617-r/org.eclipse.jgit-4.5.2.201704071617-r.jar
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.
Vulnerable Library - org.eclipse.jgit-4.5.2.201704071617-r.jar
Repository access and algorithms
Library home page: http://www.eclipse.org/jgit/
Path to dependency file: /cli/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jgit/org.eclipse.jgit/4.5.2.201704071617-r/org.eclipse.jgit-4.5.2.201704071617-r.jar
Found in HEAD commit: 012e83ee9b10e35eced839f51b8019c57f33234b
Vulnerabilities
Unreachable
Unreachable
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2016-5725
### Vulnerable Library - jsch-0.1.53.jarJSch is a pure Java implementation of SSH2
Library home page: http://www.jcraft.com/jsch/
Path to dependency file: /cli/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/com/jcraft/jsch/0.1.53/jsch-0.1.53.jar
Dependency Hierarchy: - org.eclipse.jgit-4.5.2.201704071617-r.jar (Root Library) - :x: **jsch-0.1.53.jar** (Vulnerable Library)
Found in HEAD commit: 012e83ee9b10e35eced839f51b8019c57f33234b
Found in base branch: main
### Reachability AnalysisThe vulnerable code is unreachable
### Vulnerability DetailsDirectory traversal vulnerability in JCraft JSch before 0.1.54 on Windows, when the mode is ChannelSftp.OVERWRITE, allows remote SFTP servers to write to arbitrary files via a ..\ (dot dot backslash) in a response to a recursive GET command.
Publish Date: 2017-01-19
URL: CVE-2016-5725
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 1.1%
### CVSS 4 Score Details (8.2)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: N/A - Impact Metrics: - Confidentiality Impact: N/A - Integrity Impact: N/A - Availability Impact: N/A
For more information on CVSS4 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5725
Release Date: 2017-01-19
Fix Resolution (com.jcraft:jsch): 0.1.54
Direct dependency fix Resolution (org.eclipse.jgit:org.eclipse.jgit): 4.7.0.201704051617-r
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.CVE-2023-4759
### Vulnerable Library - org.eclipse.jgit-4.5.2.201704071617-r.jarRepository access and algorithms
Library home page: http://www.eclipse.org/jgit/
Path to dependency file: /cli/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jgit/org.eclipse.jgit/4.5.2.201704071617-r/org.eclipse.jgit-4.5.2.201704071617-r.jar
Dependency Hierarchy: - :x: **org.eclipse.jgit-4.5.2.201704071617-r.jar** (Vulnerable Library)
Found in HEAD commit: 012e83ee9b10e35eced839f51b8019c57f33234b
Found in base branch: main
### Reachability AnalysisThe vulnerable code is unreachable
### Vulnerability DetailsArbitrary 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.
Publish Date: 2023-09-12
URL: CVE-2023-4759
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 0.2%
### CVSS 4 Score Details (7.7)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: N/A - Scope: N/A - Impact Metrics: - Confidentiality Impact: N/A - Integrity Impact: N/A - Availability Impact: N/A
For more information on CVSS4 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/advisories/GHSA-3p86-9955-h393
Release Date: 2023-09-12
Fix Resolution: 5.13.3.202401111512-r
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.:rescue_worker_helmet:Automatic Remediation will be attempted for this issue.