Find, fix and prevent vulnerabilities in your code.
high severity
- Vulnerable module: org.eclipse.jgit:org.eclipse.jgit
- Introduced through: org.eclipse.jgit:org.eclipse.jgit@5.11.0.202103091610-r
Detailed paths
-
Introduced through: jgitver/jgitver@jgitver/jgitver#f02ab852cb8409fd01eb47e9cdd6b3655fde1fb7 › org.eclipse.jgit:org.eclipse.jgit@5.11.0.202103091610-rRemediation: Upgrade to org.eclipse.jgit:org.eclipse.jgit@5.13.3.202401111512-r.
Overview
Affected versions of this package are vulnerable to Improper Handling of Case Sensitivity via the DirCacheCheckout
, ResolveMerger
(via its WorkingTreeUpdater
), PullCommand
using merge, and when applying a patch (PatchApplier
). An attacker can write a file to locations outside the working tree on case-insensitive filesystems. This can lead to remote code execution if the written file is a git filter that gets executed on a subsequent git command.
Note: This is only exploitable if the user performing the clone or checkout has the rights to create symbolic links, and symbolic links are enabled in the git configuration.
Workaround:
The issue can be mitigated by disabling symbolic links in the git configuration.
Remediation
Upgrade org.eclipse.jgit:org.eclipse.jgit
to version 5.13.3.202401111512-r, 6.6.1.202309021850-r or higher.
References
medium severity
- Vulnerable module: commons-io:commons-io
- Introduced through: org.apache.maven.shared:maven-script-interpreter@1.3
Detailed paths
-
Introduced through: jgitver/jgitver@jgitver/jgitver#f02ab852cb8409fd01eb47e9cdd6b3655fde1fb7 › org.apache.maven.shared:maven-script-interpreter@1.3 › commons-io:commons-io@2.6Remediation: Upgrade to org.apache.maven.shared:maven-script-interpreter@1.4.
Overview
commons-io:commons-io is a The Apache Commons IO library contains utility classes, stream implementations, file filters, file comparators, endian transformation classes, and much more.
Affected versions of this package are vulnerable to Directory Traversal via calling the method FileNameUtils.normalize using an improper string like //../foo
or \\..\foo
, which may allow access to files in the parent directory.
Details
A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.
Directory Traversal vulnerabilities can be generally divided into two types:
- Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.
st
is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public
route.
If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.
curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa
Note %2e
is the URL encoded version of .
(dot).
- Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as
Zip-Slip
.
One way to achieve this is by using a malicious zip
archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.
The following is an example of a zip
archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/
overwriting the authorized_keys
file:
2018-04-15 22:04:29 ..... 19 19 good.txt
2018-04-15 22:04:42 ..... 20 20 ../../../../../../root/.ssh/authorized_keys
Remediation
Upgrade commons-io:commons-io
to version 2.7 or higher.