A flaw was found in the cluster-curator-controller component of multicluster engine (MCE). A tenant with create or update permissions on ClusterCurator resources can inject an arbitrary Job specification. This is possible because the CreateJob() function does not validate user-controlled input when unmarshaling the spec.install.overrideJob raw extension. Successful exploitation allows the injected Job to run with the controller's elevated privileges, leading to arbitrary code execution and privilege escalation, potentially accessing cluster-wide secrets.
Security readout for executives and security teams
Plain-English summary
A low-privileged tenant who can create or update ClusterCurator resources may cause the controller to run an attacker-controlled Kubernetes Job with elevated privileges. This could enable code execution, privilege escalation, and access to cluster-wide secrets. The supplied sources do not identify affected version ranges or a confirmed fix.
Executive priority
Treat as an immediate access-control and remediation priority for MCE environments. The potential impact is cluster-wide compromise, although exploitation requires existing tenant permissions. Rapidly identify exposed clusters, narrow permissions, investigate suspicious controller-created Jobs, and follow Red Hat’s current remediation guidance.
Technical view
Cluster-curator-controller passes user-controlled spec.install.overrideJob data into CreateJob() without adequate validation while unmarshalling the raw extension. An authorized tenant can inject an arbitrary Job specification that inherits the controller’s elevated privileges. The issue is classified as CWE-94 and scores CVSS 3.1 9.9.
Likely exposure
Exposure requires Red Hat Multicluster Engine for Kubernetes and tenant identities permitted to create or update ClusterCurator resources. Risk is highest where those permissions are broadly delegated. Exact affected versions are not specified in the supplied evidence, so installed releases must be checked against current Red Hat guidance.
Exploitation context
The supplied record does not report confirmed exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires an authenticated tenant with ClusterCurator create or update permission, but needs no user interaction and could cross security boundaries into controller-level privileges.
Researcher notes
The trust-boundary failure is insufficient validation of a RawExtension before privileged Job creation. Important unanswered questions include affected release ranges, whether admission controls constrain injected specifications, available patches, and observable audit indicators. No exploit procedure or confirmed exploitation is provided by the source bundle.
Mitigation direction
Check Red Hat advisories for affected versions, patches, and supported remediation instructions.
Restrict ClusterCurator create and update permissions to explicitly trusted administrators.
Temporarily remove unnecessary tenant access to the vulnerable functionality.
Review controller service-account privileges and reduce them where operationally supported.
Protect and rotate cluster secrets if evidence indicates unauthorized privileged Job execution.
Validation and detection
Inventory clusters running Red Hat Multicluster Engine and record component versions.
Identify every identity permitted to create or update ClusterCurator resources.
Review ClusterCurator changes for unexpected spec.install.overrideJob content.
Inspect Jobs created by cluster-curator-controller for unusual images, commands, privileges, or secret access.
Confirm remediation status against current Red Hat guidance because affected version ranges are absent.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.