In Spring for Apache Kafka, forged retry topic headers subvert retry routing and backoff behavior
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 |
|
|
Spring Kafka's retry topic infrastructure did not sufficiently validate user-controlled header values before acting on them. A producer could send a record with a crafted retry_topic-attempts header to supply an out-of-range attempt count and cause the retry topic router to misidentify where the message was in the retry sequence.
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
Spring Kafka's retry topic infrastructure does not sufficiently validate the user-controlled retry_topic-attempts header. A producer able to send a record with a crafted header can supply an out-of-range attempt count, causing the retry topic router to misidentify the message's position in the retry sequence.
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.