Deserialization of Untrusted Data The advisory has been revoked - it doesn't affect any version of package com.jsoniter:jsoniter Open this link in a new tab

    Threat Intelligence

    Exploit Maturity
    Proof of concept
    0.08% (35th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • published 14 Sep 2021
  • disclosed 5 Jul 2021
  • credit Adi Malyanker


This was deemed not a vulnerability.


com.jsoniter:jsoniter is a jsoniter (json-iterator) is fast and flexible JSON parser.

Affected versions of this package are vulnerable to Deserialization of Untrusted Data via malicious JSON strings. This may lead to a Denial of Service, and in certain cases, code execution.


package exploit_jsonex;
public class inner {
    public Object obj;

public void setup(int id) {
    System.out.println("executed setup ");

public Object getObj() {
    System.out.println("got obj");
    return obj;
public void setObj(Object obj) {
    System.out.println("set obj");

    this.obj = obj;


String jsonString = "{\"up\":123, \"obj\":[\"org\",\"http\"]}";
Object ans =  JsonIterator.deserialize(jsonString, inner.class);


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).