https://blog.devops-monk.com/tags/deserialization/Recent content in Deserialization on Devops MonkHugoen-usMon, 04 May 2026 00:00:00 +0000https://blog.devops-monk.com/tutorials/java17/deserialization-filters/Mon, 04 May 2026 00:00:00 +0000https://blog.devops-monk.com/tutorials/java17/deserialization-filters/Finalized in Java 17 (JEP 415). Extends JEP 290 (Java 9), which introduced the basic deserialization filter API. Why Deserialization Is Dangerous Java object deserialization (ObjectInputStream.readObject()) is one of the most exploited attack surfaces in Java. When a Java application deserializes untrusted bytes, the JVM instantiates arbitrary classes and calls their methods as a side effect — before your application code even sees the result. Attackers craft gadget chains: sequences of serializable classes in common libraries (Apache Commons Collections, Spring Framework, etc.https://blog.devops-monk.com/tutorials/spring-kafka/deserialization-errors/Mon, 04 May 2026 00:00:00 +0000https://blog.devops-monk.com/tutorials/spring-kafka/deserialization-errors/The Problem: Poison Pills at Deserialization Time A malformed byte sequence — truncated JSON, wrong Avro schema, corrupt payload — throws an exception during deserialization, before the listener method is called. Without special handling, this record blocks the partition indefinitely: the consumer fetches it, fails to deserialize, and fetches it again on the next poll. sequenceDiagram participant Broker participant Container participant Deserializer loop forever without ErrorHandlingDeserializer Container->>Broker: poll() Broker-->>Container: [good-record, CORRUPT-RECORD, good-record] Container->>Deserializer: deserialize(CORRUPT-RECORD) Deserializer-->>Container: JsonProcessingException 💥 Note over Container: Partition blocked — same record on every poll end ErrorHandlingDeserializer solves this by catching the deserialization exception and wrapping it in a DeserializationException that the listener container can route to the error handler.