In Spring for Apache Kafka, unbounded delegate cache keyed on user-controlled, potentially malicious selector header
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 |
|
|
When an application opts into DelegatingDeserializer, a producer can grow the consumer's heap without bound by sending records with unique random spring.kafka.serialization.selector header values, eventually causing GC thrash and OutOfMemoryError.
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
Applications that opt into DelegatingDeserializer are vulnerable when a producer sends records with unique random spring.kafka.serialization.selector header values. This can grow the consumer's heap without bound, eventually causing GC thrash and OutOfMemoryError. The input does not specify authentication requirements or user interaction.
Check applications using 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.