CVE-2024-8285

Kroxylicious: missing upstream kafka tls hostname verification

Published Aug 30, 2024 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
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.

Remediation

Vendor 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.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2024-2592 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.
Github GHSA Github GHSA GHSA-h83p-72jv-g7vp Missing hostname validation in Kroxylicious
History
Type Values Removed Values Added
CPEs cpe:/a:redhat:amq_streams:1
Type Values Removed Values Added
CPEs cpe:/a:redhat:amq_streams:1
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N'}

cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N'}

Type Values Removed Values Added
First Time appeared Redhat kroxylicious
Weaknesses CWE-295
CPEs cpe:2.3:a:redhat:kroxylicious:-:*:*:*:*:*:*:*
Vendors & Products Redhat kroxylicious
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description No description is available for this CVE. 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.
Title kroxylicious: Missing upstream Kafka TLS hostname verification Kroxylicious: missing upstream kafka tls hostname verification
First Time appeared Redhat
Redhat amq Streams
CPEs cpe:/a:redhat:amq_streams:1
Vendors & Products Redhat
Redhat amq Streams
References
Type Values Removed Values Added
Description No description is available for this CVE.
Title kroxylicious: Missing upstream Kafka TLS hostname verification
Weaknesses CWE-297
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N'}

threat_severity

Moderate

Weaknesses

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Nov 20, 2025, 8:57 PM
Reserved
Aug 28, 2024, 7:38 PM
Status
Modified
Published
Aug 30, 2024, 10:15 PM
Modified
Jun 17, 2026, 8:22 AM
Severity
Moderate
Public date
Aug 27, 2024, 12:00 AM