HawkScan Test Info for Java Serialization Object

Java Serialization Object


Plugin Id: 90002


To mitigate the vulnerability related to the “Java Serialization Object,” the following steps can be taken:

  1. Disable Java Serialization: If Java Serialization is not required for the application, it is recommended to disable it completely. This can be achieved by configuring the application server or framework to disallow the deserialization of objects.

    Example for Apache Tomcat’s context.xml file:

      <Manager className="org.apache.catalina.session.PersistentManager">
        <Store className="org.apache.catalina.session.FileStore" />
  2. Implement Input Validation: Ensure that all user-supplied input is properly validated and sanitized before being used in the deserialization process. This includes input from HTTP requests, databases, or any other external sources.

    Example in Java using Apache Commons Validator:

    import org.apache.commons.validator.routines.EmailValidator;
    public class User {
      private String email;
      public void setEmail(String email) {
        if (EmailValidator.getInstance().isValid(email)) {
          this.email = email;
        } else {
          throw new IllegalArgumentException("Invalid email address");
  3. Use a Secure Serialization Library: If Java Serialization is required, consider using a secure serialization library that provides additional safeguards against deserialization vulnerabilities. Libraries like Google’s Protocol Buffers or Apache Avro can be used as alternatives to Java Serialization.


Java Serialization is a mechanism in Java that allows objects to be converted into a stream of bytes and vice versa. It is commonly used for various purposes, such as data persistence, network communication, and distributed computing. However, if not properly validated, it can introduce security vulnerabilities, including remote code execution.

The vulnerability occurs when an attacker is able to send a specially crafted object to the application, which is then deserialized without proper validation. This can lead to the execution of arbitrary code on the server, potentially compromising the entire system.

The presence of a magic sequence identifying Java Serialization Objects (JSO) has been detected in the application’s code or network traffic. This magic sequence is represented as “rO0AB” in Base64 or as the raw bytes “0xac, 0xed, 0x00, 0x05”. Its presence indicates that the application is using Java Serialization and may be susceptible to the associated vulnerabilities.


The risks associated with the “Java Serialization Object” vulnerability are significant and can have severe consequences for the affected system:

  1. Remote Code Execution: Exploiting this vulnerability allows an attacker to execute arbitrary code on the server. This can lead to complete compromise of the system, unauthorized access to sensitive data, or the ability to launch further attacks within the network.

  2. Data Manipulation: By crafting malicious objects, an attacker can manipulate the deserialization process to modify data within the application. This can result in data integrity issues, unauthorized changes to critical information, or the ability to bypass security controls.

  3. Denial of Service: An attacker can exploit the vulnerability to cause a denial of service by sending a large number of specially crafted objects. This can overwhelm the server’s resources, leading to system instability, unresponsiveness, or even a complete shutdown.

It is crucial to address this vulnerability promptly to prevent potential exploitation and protect the integrity, confidentiality, and availability of the system and its data.