CyberKit

Insecure Deserialization

Also called deserialization vulnerability.

Rebuilding objects from untrusted data, enabling code execution.

What it is

A vulnerability where untrusted serialized data is deserialized into objects without validation. Crafted payloads can instantiate dangerous object graphs or invoke gadget chains that lead to code execution or other abuse.

Why it matters

Insecure deserialization is a frequent path to RCE in enterprise applications and a common audit finding. Detecting it often means watching for unusual serialized blobs reaching deserializers.

In practice

An application deserializes a user-supplied token, and a crafted object chain triggers method calls that run system commands.

What to look for

  • Serialized objects in cookies, parameters or message queues.
  • Known gadget libraries in the classpath.
  • Deserialization errors in application logs.

Common mistake

Filtering class names with a deny list. Use an allow list or avoid native deserialization.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Burp Suite Commercial

    An intercepting proxy for testing web apps by hand and with its scanner.

  • ZAP Open source

    An open source web app scanner and proxy, often run in CI pipelines.

  • Cloudflare WAF Commercial

    Blocks common web attacks at the edge while the code gets fixed.

Read next

Sources