Impacted versions:
- Confluent Platform < 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3
Recommended action:
- Customers running Kafka Streams applications should upgrade the Kafka Streams library to the version shipped with the latest patched Confluent Platform release.
- As defense in depth, keep log.message.timestamp.after.max.ms bound on source topics and restrict write access to them.
Issue:
A security vulnerability has been identified in the Apache Kafka streams timestamp handling. Kafka Streams derives its stream-time clock from record timestamps. When it computes the next stream-time punctuation, the calculation has no overflow check. A record with a timestamp at or near the maximum 64-bit value advances stream time to that value, so the next punctuation time overflows to a negative number. The punctuation queue then re-queues that time and loops on it indefinitely while holding a lock, which stalls the stream thread. As a result, an authenticated attacker capable of writing to a topic can cause the Kafka Streams to stop processing, resulting in a loss of availability.
Remediation:
- Confluent Platform: This issue is resolved in the following versions of Confluent Platform: 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3
CVSS Scores:
-
Confluent Platform: 5.7 (CVSS v3.1 Calculator)