RHSA-2025:2416HighCVSS 7.5

Red Hat Security Advisory: Streams for Apache Kafka 2.9.0 release and security update

Published
March 5, 2025
Last Modified
October 15, 2026

🔗 CVE IDs covered (7)

CVE-2024-31141 →CVE-2024-47535 →CVE-2024-47554 →CVE-2023-52428 →CVE-2024-8184 →CVE-2024-9355 →CVE-2024-24791 →

📋 Description

CVE-2023-52428 — nimbus-jose-jwt: large JWE p2c header value causes Denial of Service CVE-2024-8184 — org.eclipse.jetty:jetty-server: jetty: Jetty ThreadLimitHandler.getRemote() vulnerable to remote DoS attacks CVE-2024-9355 — golang-fips: Golang FIPS zeroed buffer CVE-2024-24791 — net/http: Denial of service due to improper 100-continue handling in net/http CVE-2024-31141 — kafka-clients: privilege escalation to filesystem read-access via automatic ConfigProvider CVE-2024-47535 — netty: Denial of Service attack on windows app using Netty CVE-2024-47554 — apache-commons-io: Possible denial of service attack on untrusted input to XmlStreamReader

🎯 Affected products1

  • Streams for Apache Kafka 2.9.0

✅ Remediation

Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: For applications in which an untrusted party can specify Apache Kafka Client configuration, disable automatic configuration providers by setting the JVM system property org.apache.kafka.automatic.config.providers=none. For Kafka Connect workers that must use the listed providers, restrict them with appropriate allowlist.pattern and allowed.paths settings. Upgrade kafka-clients to version 3.8.0 or later, or apply the applicable vendor fix. The system-property restriction is not recommended for Kafka Clients or Kafka Connect deployments where users are trusted with disk and environment access, or for Kafka Broker, Kafka MirrorMaker 2.0, Kafka Streams, and Kafka command-line tools. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

🔗 References (10)