Kafka traffic interception via unchecked TLS hostname
Published Aug 30, 2024 · Updated Nov 20, 2025
Improper TLS hostname validation in Kroxylicious before 0.8.0 allows man-in-the-middle attackers to intercept upstream Kafka traffic. The upstream connection setup accepts a trusted certificate without checking that its identity matches the configured Kafka broker hostname. An attacker must control a network path, DNS, routing, a peer system, or proxy configuration; successful interception exposes and permits modification of proxied data.
Summary
What happened
Improper TLS hostname validation in Kroxylicious before 0.8.0 allows man-in-the-middle attackers to intercept upstream Kafka traffic. The upstream connection setup accepts a trusted certificate without checking that its identity matches the configured Kafka broker hostname. An attacker must control a network path, DNS, routing, a peer system, or proxy configuration; successful interception exposes and permits modification of proxied data.
The record
- CVE
- CVE-2024-8285
- Published
- Aug 30, 2024
- Updated
- Nov 20, 2025
- Vendor
- Red Hat
- Product
- Kroxylicious
- Classifications
- CWE-297, CWE-295, T1557
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Aug 30, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.80.0 <0.80.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo