Skip to main content
CVE-2024-6104VulnerabilityPublished Updated

Red Hat Security Advisory: Multicluster Engine for Kubernetes 2.5.7 security updates and bug fixes

Affects Red HatSource GCVE Database

0
Compare

Mentioned vulnerabilities

Not known to be exploited.

Data as of 29 Oct 2026, 09:11 UTC

Severity
Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Product Security Red HatAffected
  • Red Hat
  • multicluster engine for Kubernetes
  • multicluster engine for Kubernetes 2.5 for RHEL 9
  • multicluster engine for Kubernetes 2.5 for RHEL 8
  • ppc64le
Fixed in–

Description

Multicluster engine for Kubernetes v2.5.7 images Multicluster engine for Kubernetes provides the foundational components that are necessary for the centralized management of multiple Kubernetes-based clusters across data centers, public clouds, and private clouds. You can use the engine to create new Red Hat OpenShift Container Platform clusters or to bring existing Kubernetes-based clusters under management by importing them. After the clusters are managed, you can use the APIs that are provided by the engine to distribute configuration based on placement policy. Security fix(es): CVE-2024-42459 nodejs/elliptic: EDDSA signature malleability occurs because there is a missing signature length check, and thus zero-valued bytes can be removed or appended CVE-2024-42460 nodejs/elliptic: ECDSA signature malleability occurs because there is a missing check for whether the leading bit of r and s is zero CVE-2024-42461 nodejs/elliptic: ECDSA implementation malleability due to BER-enconded signatures being allowed CVE-2024-6104 go-retryablehttp: url might write sensitive information to log file

References

Community reviews

Loading reviews…