In Spring for Apache Kafka, overly broad trusted-package matching in header mappers exposes JDK classes to deserialization
Spring for Apache Kafka
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.kafka:spring-kafka Maven |
|
|
Spring for Apache Kafka
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.kafka:spring-kafka Maven |
|
|
JsonKafkaHeaderMapper and the deprecated DefaultKafkaHeaderMapper matched type headers against trusted packages using a prefix check, meaning that trusting any package implicitly trusted all of its subpackages. Combined with Jackson's default bean deserialization, a producer could supply crafted header values that caused the consumer to deserialize arbitrary JDK types.
Affected versions: Spring for Apache Kafka 4.0.0 through 4.0.5; 3.3.0 through 3.3.15; 3.2.0 through 3.2.13; 2.9.0 through 2.9.13; 2.8.0 through 2.8.11.
From the CVE record · vmware
JsonKafkaHeaderMapper and the deprecated DefaultKafkaHeaderMapper use a prefix check for trusted packages, unintentionally trusting their subpackages. A producer that supplies crafted header values can cause a consumer to deserialize arbitrary JDK types when the consumer trusts a matching package.
Teams running Spring for Apache Kafka 4.0.0–4.0.5, 3.3.0–3.3.15, 3.2.0–3.2.13, 2.9.0–2.9.13, or 2.8.0–2.8.11 should check their deployments.