Skip to content
TrackPodcasts
newsMar 12, 20263:01

What Is Insecure Deserialization

About this episode

An overview of cybersecurity Insecure Deserialization, focussing on introduction to insecure deserialization

Interactive timestamps

Jump to segment

Get every episode summarized

Each time Daily Cyber Security News publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.

Email me new episodes

Free for 3 shows. No card needed.

Hosts & guests

Transcript ready

30 searchable segments. Every word is indexed and playable.

What Is Insecure Deserialization

Daily Cyber Security News

0:00
3:01

Full transcript

Daily Cyber Security NewsWhat Is Insecure Deserialization. Machine-transcribed; use the interactive transcript above to jump the player to any line.

0:00Serialization converts in-memory objects and data structures into a format that can be stored, sent over a network, or written to disk. De-serialization reverses that process by rebuilding the original objects from the stored or transmitted data. These two fundamental operations power data exchange and persistence across applications, but they also introduce risk when untrusted inputs are deserialized without proper validation or safeguards. Insecure deserialization occurs when an application accepts serialized data from an untrusted source and reconstructs it without verifying its integrity or content. Attackers can craft or modify that data to trigger unauthorized actions, such as executing code, escalating privileges, or bypassing authentication, making this vulnerability especially dangerous for modern web and distributed applications. Attackers craft or modify serialized objects to include malicious instructions or tampered

1:02properties. When the application rebuilds these objects without verification, it can unintentionally execute internal methods, bypass authentication checks, or elevate privileges. By linking existing code paths into a sequence of operations, often called a gadget chain, an attacker turns trusted components into tools for executing unauthorized actions. Recognizing how untrusted data can trigger these exploit paths is essential for effective defense. Major incidents have highlighted the real impact of insecure deserialization. In 2015, Attackers exploited a gadget chain in the Apache Commons collections library to execute arbitrary code on countless Java servers. In 2017, a floor in the Ruby on Rails YAML parser allowed crafted input to bypass authentication checks and leak sensitive data. Vulnerable WordPress plugins that used PHP's native unserialized function were manipulated to

2:07override files and deface sites. In 2018, a deserialization weakness in the Jenkins Continuous Integration Tool let remote actors deploy malware on build machines. These events demonstrate how unvalidated object reconstruction can lead to full system compromise. In the upcoming videos, we will explore practical exploitation techniques to demonstrate how in secure deserialization attacks are crafted and executed. Next, we will examine common development platforms and libraries where these vulnerabilities frequently appear. Then you will learn methods for detecting and assessing deserialization weaknesses in your own applications. Finally, we will cover best practices and safeguards to prevent these attacks and mitigate risk in both new and existing code bases.

More episodes

More from Daily Cyber Security News

View all episodes →