CVE-2024-8285 is a high-severity (CVSS 7.3) CWE-297 vulnerability in io.kroxylicious:kroxylicious-runtime. A fix is available for io.kroxylicious:kroxylicious-runtime — see the affected versions and patch details below.
Missing hostname validation in Kroxylicious
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-8285.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.kroxylicious:kroxylicious-runtimeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.kroxylicious:kroxylicious-runtime | all versions | 0.8.0io.kroxylicious:kroxylicious-runtime:0.8.0 |
Affected Products
kroxyliciousredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.kroxylicious:kroxylicious-runtime, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.kroxylicious:kroxylicious-runtime to 0.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-8285 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat have considered this vulnerability as a 'Moderate' severity given the complexity and the permission level required to perform a successful attacker.
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.Source: Red Hat security advisory for CVE-2024-8285 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Streams for Apache Kafka 2.8.0 | io.kroxylicious-kroxylicious-parent | RHSA-2024:9571 |
Frequently Asked Questions
Is CVE-2024-8285 in your dependencies?
Find it across Maven, including transitive dependencies.