Kroxylicious: missing upstream kafka tls hostname verification
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| unaffected |
|
||||||||
| Red Hat | Streams for Apache Kafka 2.8.0 | unaffected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — | ||||||
| Red Hat | streams for Apache Kafka | affected | — |
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Streams for Apache Kafka 2.8.0 | |||
| io.kroxylicious-kroxylicious-parent | cpe:/a:redhat:amq_streams:2 | RHSA-2024:9571 | 2024-11-13T00:00:00Z |
No data available yet.
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.
| Source | ID | Title |
|---|---|---|
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 |
GHSA-h83p-72jv-g7vp | Missing hostname validation in Kroxylicious |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.378% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:amq_streams:1 |
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs |
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:amq_streams:2 | |
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
cvssV3_1
|
| 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
|
| 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
|
cvssV3_1
|