In Spring for Apache Kafka, forged retry topic headers subvert retry routing and backoff behavior
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.8.12, 2.9.14, 3.2.14 and 2 more.
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.
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