In Spring for Apache Kafka, overly broad trusted-package matching in header mappers exposes JDK classes to deserialization
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 2.8.12, 2.9.14, 3.2.14 and 2 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Spring | >=2.8.0 <2.8.12, >=2.9.0 <2.9.14, >=3.2.0 <3.2.14, >=3.3.0 <3.3.15.1, >=4.0.0 <4.0.5.1 | 2.8.12, 2.9.14, 3.2.14, 3.3.15.1, 4.0.5.1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket