Find, fix and prevent vulnerabilities in your code.
critical severity
- Vulnerable module: org.apache.maven.shared:maven-shared-utils
- Introduced through: org.apache.maven:maven-core@3.6.0
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.apache.maven.shared:maven-shared-utils@3.2.1Remediation: Upgrade to org.apache.maven:maven-core@3.8.2.
Overview
org.apache.maven.shared:maven-shared-utils is a functional replacement for plexus-utils in Maven.
Affected versions of this package are vulnerable to Command Injection. The Commandline
class can emit double-quoted strings without proper escaping, allowing shell injection attacks. The BourneShell
class should unconditionally single-quote emitted strings (including the name of the command itself being quoted), with {{'"'"'}}
used for embedded single quotes, for maximum safety across shells implementing a superset of POSIX quoting rules.
This is a similar issue to SNYK-JAVA-ORGCODEHAUSPLEXUS-31522
Remediation
Upgrade org.apache.maven.shared:maven-shared-utils
to version 3.3.3 or higher.
References
high severity
- Vulnerable module: org.apache.commons:commons-lang3
- Introduced through: org.apache.commons:commons-lang3@3.9, org.apache.maven:maven-core@3.6.0 and others
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.commons:commons-lang3@3.9Remediation: Upgrade to org.apache.commons:commons-lang3@3.18.0.
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.apache.commons:commons-lang3@3.9Remediation: Upgrade to org.apache.maven:maven-core@3.9.8.
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.velocity:velocity-engine-core@2.1 › org.apache.commons:commons-lang3@3.9
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven.plugin-tools:maven-plugin-annotations@3.6.0 › org.apache.maven:maven-artifact@3.6.0 › org.apache.commons:commons-lang3@3.9Remediation: Upgrade to org.apache.maven.plugin-tools:maven-plugin-annotations@3.6.2.
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-plugin-api@3.6.0 › org.apache.maven:maven-artifact@3.6.0 › org.apache.commons:commons-lang3@3.9Remediation: Upgrade to org.apache.maven:maven-plugin-api@3.9.8.
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.apache.maven:maven-artifact@3.6.0 › org.apache.commons:commons-lang3@3.9Remediation: Upgrade to org.apache.maven:maven-core@3.9.8.
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.apache.maven:maven-model-builder@3.6.0 › org.apache.maven:maven-artifact@3.6.0 › org.apache.commons:commons-lang3@3.9Remediation: Upgrade to org.apache.maven:maven-core@3.9.8.
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.apache.maven:maven-plugin-api@3.6.0 › org.apache.maven:maven-artifact@3.6.0 › org.apache.commons:commons-lang3@3.9Remediation: Upgrade to org.apache.maven:maven-core@3.9.8.
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.apache.maven:maven-resolver-provider@3.6.0 › org.apache.maven:maven-model-builder@3.6.0 › org.apache.maven:maven-artifact@3.6.0 › org.apache.commons:commons-lang3@3.9Remediation: Upgrade to org.apache.maven:maven-core@3.9.8.
Overview
Affected versions of this package are vulnerable to Uncontrolled Recursion via the ClassUtils.getClass
function. An attacker can cause the application to terminate unexpectedly by providing excessively long input values.
Remediation
Upgrade org.apache.commons:commons-lang3
to version 3.18.0 or higher.
References
high severity
- Vulnerable module: commons-beanutils:commons-beanutils
- Introduced through: commons-beanutils:commons-beanutils@1.9.4
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › commons-beanutils:commons-beanutils@1.9.4Remediation: Upgrade to commons-beanutils:commons-beanutils@1.11.0.
Overview
commons-beanutils:commons-beanutils is a provides an easy-to-use but flexible wrapper around reflection and introspection.
Affected versions of this package are vulnerable to Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') via the getProperty
and getNestedProperty
methods of the PropertyUtilsBean
class. An attacker can execute arbitrary code by accessing the declaredClass
property of Java enum objects, which allows access to the ClassLoader.
Note:
The BeanIntrospector
class that can mitigate this vulnerability was added in version 1.9.2 but its usage was not enabled by default.
Remediation
Upgrade commons-beanutils:commons-beanutils
to version 1.11.0 or higher.
References
high severity
- Vulnerable module: org.apache.velocity:velocity-engine-core
- Introduced through: org.apache.velocity:velocity-engine-core@2.1
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.velocity:velocity-engine-core@2.1Remediation: Upgrade to org.apache.velocity:velocity-engine-core@2.3.
Overview
org.apache.velocity:velocity-engine-core is a template engine written in Java.
Affected versions of this package are vulnerable to Arbitrary Code Execution. An attacker that is able to modify Velocity templates may execute arbitrary Java code or run arbitrary system commands with the same privileges as the account running the Servlet container. This applies to applications that allow untrusted users to upload/modify velocity templates running Apache Velocity Engine.
Note
Users of org.apache.velocity:velocity
should update to org.apache.velocity:velocity-engine-core
version 2.3 to mitigate this vulnerability.
Remediation
Upgrade org.apache.velocity:velocity-engine-core
to version 2.3 or higher.
References
high severity
- Vulnerable module: org.json:json
- Introduced through: org.json:json@20190722
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.json:json@20190722Remediation: Upgrade to org.json:json@20231013.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling. An attacker can cause indefinite amounts of memory to be used by inputting a string of modest size. This can lead to a Denial of Service.
PoC
package orgjsonbug;
import org.json.JSONObject;
/**
* Illustrates a bug in JSON-Java.
*/
public class Bug {
private static String makeNested(int depth) {
if (depth == 0) {
return "{\"a\":1}";
}
return "{\"a\":1;\t\0" + makeNested(depth - 1) + ":1}";
}
public static void main(String[] args) {
String input = makeNested(30);
System.out.printf("Input string has length %d: %s\n", input.length(), input);
JSONObject output = new JSONObject(input);
System.out.printf("Output JSONObject has length %d: %s\n", output.toString().length(), output);
}
}
Remediation
Upgrade org.json:json
to version 20231013 or higher.
References
high severity
- Vulnerable module: org.json:json
- Introduced through: org.json:json@20190722
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.json:json@20190722Remediation: Upgrade to org.json:json@20230227.
Overview
Affected versions of this package are vulnerable to Denial of Service (DoS) in the XML.toJSONObject
component via crafted JSON
or XML
data.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
ws
package
Remediation
Upgrade org.json:json
to version 20230227 or higher.
References
high severity
- Vulnerable module: org.apache.maven:maven-core
- Introduced through: org.apache.maven:maven-core@3.6.0
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0Remediation: Upgrade to org.apache.maven:maven-core@3.8.1.
Overview
Affected versions of this package are vulnerable to Resources Downloaded over Insecure Protocol. Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls.
If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. For more information about repository management, visit this page.
Remediation
Upgrade org.apache.maven:maven-core
to version 3.8.1 or higher.
References
medium severity
- Vulnerable module: commons-io:commons-io
- Introduced through: org.apache.maven:maven-core@3.6.0
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.apache.maven.shared:maven-shared-utils@3.2.1 › commons-io:commons-io@2.6
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 Uncontrolled Resource Consumption ('Resource Exhaustion') through the XmlStreamReader
class. An attacker can cause the application to consume excessive CPU resources by sending specially crafted XML content.
Remediation
Upgrade commons-io:commons-io
to version 2.14.0 or higher.
References
medium severity
- Vulnerable module: commons-io:commons-io
- Introduced through: org.apache.maven:maven-core@3.6.0
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.apache.maven.shared:maven-shared-utils@3.2.1 › commons-io:commons-io@2.6Remediation: Upgrade to org.apache.maven:maven-core@3.9.7.
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.
References
medium severity
- Module: junit:junit
- Introduced through: junit:junit@4.13.1
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › junit:junit@4.13.1
EPL-1.0 license
medium severity
- Module: org.eclipse.sisu:org.eclipse.sisu.inject
- Introduced through: org.apache.maven:maven-core@3.6.0 and org.apache.maven:maven-plugin-api@3.6.0
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.eclipse.sisu:org.eclipse.sisu.inject@0.3.3
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-plugin-api@3.6.0 › org.eclipse.sisu:org.eclipse.sisu.plexus@0.3.3 › org.eclipse.sisu:org.eclipse.sisu.inject@0.3.3
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.eclipse.sisu:org.eclipse.sisu.plexus@0.3.3 › org.eclipse.sisu:org.eclipse.sisu.inject@0.3.3
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.apache.maven:maven-plugin-api@3.6.0 › org.eclipse.sisu:org.eclipse.sisu.plexus@0.3.3 › org.eclipse.sisu:org.eclipse.sisu.inject@0.3.3
EPL-1.0 license
medium severity
- Module: org.eclipse.sisu:org.eclipse.sisu.plexus
- Introduced through: org.apache.maven:maven-plugin-api@3.6.0 and org.apache.maven:maven-core@3.6.0
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-plugin-api@3.6.0 › org.eclipse.sisu:org.eclipse.sisu.plexus@0.3.3
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.eclipse.sisu:org.eclipse.sisu.plexus@0.3.3
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › org.apache.maven:maven-plugin-api@3.6.0 › org.eclipse.sisu:org.eclipse.sisu.plexus@0.3.3
EPL-1.0 license
low severity
- Vulnerable module: com.google.guava:guava
- Introduced through: org.apache.maven:maven-core@3.6.0
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › com.google.inject:guice@4.2.1 › com.google.guava:guava@25.1-android
Overview
com.google.guava:guava is a set of core libraries that includes new collection types (such as multimap and multiset,immutable collections, a graph library, functional types, an in-memory cache and more.
Affected versions of this package are vulnerable to Creation of Temporary File in Directory with Insecure Permissions due to the use of Java's default temporary directory for file creation in FileBackedOutputStream
. Other users and apps on the machine with access to the default Java temporary directory can access the files created by this class. This more fully addresses the underlying issue described in CVE-2020-8908, by deprecating the permissive temp file creation behavior.
NOTE: Even though the security vulnerability is fixed in version 32.0.0, the maintainers recommend using version 32.0.1, as version 32.0.0 breaks some functionality under Windows.
Remediation
Upgrade com.google.guava:guava
to version 32.0.0-android, 32.0.0-jre or higher.
References
low severity
- Vulnerable module: com.google.guava:guava
- Introduced through: org.apache.maven:maven-core@3.6.0
Detailed paths
-
Introduced through: aposin/LicenseScout@aposin/LicenseScout#13779b90b74c5c33e1b7764cafdd7c6dc8ca01b1 › org.apache.maven:maven-core@3.6.0 › com.google.inject:guice@4.2.1 › com.google.guava:guava@25.1-android
Overview
com.google.guava:guava is a set of core libraries that includes new collection types (such as multimap and multiset,immutable collections, a graph library, functional types, an in-memory cache and more.
Affected versions of this package are vulnerable to Information Disclosure.
The file permissions on the file created by com.google.common.io.Files.createTempDir
allow an attacker running a malicious program co-resident on the same machine to steal secrets stored in this directory. This is because, by default, on unix-like operating systems the /tmp directory is shared between all users, so if the correct file permissions aren't set by the directory/file creator, the file becomes readable by all other users on that system.
PoC
File guavaTempDir = com.google.common.io.Files.createTempDir();
System.out.println("Guava Temp Dir: " + guavaTempDir.getName());
runLS(guavaTempDir.getParentFile(), guavaTempDir); // Prints the file permissions -> drwxr-xr-x
File child = new File(guavaTempDir, "guava-child.txt");
child.createNewFile();
runLS(guavaTempDir, child); // Prints the file permissions -> -rw-r--r--
For Android developers, choosing a temporary directory API provided by Android is recommended, such as context.getCacheDir()
. For other Java developers, we recommend migrating to the Java 7 API java.nio.file.Files.createTempDirectory()
which explicitly configures permissions of 700, or configuring the Java runtime's java.io.tmpdir system property to point to a location whose permissions are appropriately configured.
Remediation
There is no fix for com.google.guava:guava
. However, in version 30.0 and above, the vulnerable functionality has been deprecated. In oder to mitigate this vulnerability, upgrade to version 30.0 or higher and ensure your dependencies don't use the createTempDir or createTempFile methods.