Description
A flaw was found in Kroxylicious. When establishing the connection with the upstream Kafka server using a TLS secured connection, Kroxylicious fails to properly verify the server's hostname, resulting in an insecure connection. For a successful attack to be performed, the attacker needs to perform a Man-in-the-Middle attack or compromise any external systems, such as DNS or network routing configuration. This issue is considered a high complexity attack, with additional high privileges required, as the attack would need access to the Kroxylicious configuration or a peer system. The result of a successful attack impacts both data integrity and confidentiality.
Metrics
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| — | — | >= 0.80.0, < 0.80.0 |
| Red Hat | Streams for Apache Kafka 2.8.0 | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
| Red Hat | streams for Apache Kafka | — |
References
- https://access.redhat.com/errata/RHSA-2024:9571
- https://access.redhat.com/security/cve/CVE-2024-8285Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2308606Issue Tracking, Vendor Advisory
Timeline
- Published
- Aug 30, 2024
- Last modified
- Jun 17, 2026
- NVD status
- Modified