Kroxylicious: missing upstream kafka tls hostname verification
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
io.kroxylicious:kroxylicious-runtimeMaven | < 0.8.0 | 0.8.0 |
Affected products
2- Range: < 0.8.0
Patches
Vulnerability mechanics
References
6- access.redhat.com/errata/RHSA-2024:9571ghsavendor-advisoryx_refsource_REDHATWEB
- github.com/advisories/GHSA-h83p-72jv-g7vpghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2024-8285ghsaADVISORY
- access.redhat.com/security/cve/CVE-2024-8285ghsavdb-entryx_refsource_REDHATWEB
- bugzilla.redhat.com/show_bug.cgighsaissue-trackingx_refsource_REDHATWEB
- github.com/kroxylicious/kroxylicious/commit/8be1efcb0a2160fa3ad4cb0e5a27e60160774dceghsaWEB
News mentions
0No linked articles in our index yet.