Eclipse Ankaios
Monthly
A local unprivileged user can hijack the Control Interface of another workload in Eclipse Ankaios 0.1.0 through 1.0.2 by pre-creating the agent's predictable run-folder path hierarchy and Control Interface FIFOs under the shared default location `$TMPDIR/ankaios`. Because the agent reuses an existing directory or FIFO based only on an existence/file-type check — without verifying ownership or permissions — it treats the attacker-owned pipes as the legitimate Control Interface and executes requests under that workload's configured `controlInterfaceAccess` permissions, enabling workload impersonation and unauthorized reading or modification of the cluster's desired state. The flaw is CWE-379 (insecure temporary file/permissions), carries a CVSS 4.0 base score of 8.4 (AV:L/PR:L/AT:P, high confidentiality and integrity impact), and has no public exploit code or CISA KEV listing at time of analysis; EPSS is 0.09%, consistent with a local, non-automatable attack. The vendor released v1.0.3 with an ownership/permission validation check (PR #799).
Incorrect authorization in Eclipse Ankaios v0.5.1-v1.0.1 allows an authenticated workload to bypass its scoped access restrictions on the agent-side Control Interface. When the cluster is configured with multi-segment allow rules whose first path segment is a wildcard (e.g., `*.workloads.some_workload`), submitting a CompleteStateRequest or UpdateStateRequest with an empty field mask is incorrectly evaluated as matching the scoped rule, granting the workload full read or write access beyond its authorized state subtree. No public exploit is identified at time of analysis; a patched release (v1.0.2) is available.
Local attackers holding a low-privileged workload on an Eclipse Ankaios agent can bypass log-access authorization to read other workloads' logs on the same agent. The flaw affects Eclipse Ankaios 0.6.0 through 1.0.3, where the agent's control-interface authorizer stops evaluating a rule at the first wildcard pattern and therefore skips later deny LogRule entries; exploitation requires a rule set in which a wildcard-containing entry precedes a deny rule. This is a low-severity authorization flaw (CVSS 4.8, CWE-863) requiring local access and an existing workload foothold, with no public exploit identified at time of analysis.
Uncontrolled memory allocation in Eclipse Ankaios 0.1.0-1.0.1 allows a workload with granted Control Interface access to abort the agent process by declaring an arbitrarily large protobuf message length over the Control Interface FIFO, causing unbounded heap allocation and an OOM-triggered process crash. The impact is complete loss of orchestration services for all workloads managed by the affected agent instance. No public exploit has been identified and no active exploitation is confirmed; patch v1.0.2 is available.
A local unprivileged user can hijack the Control Interface of another workload in Eclipse Ankaios 0.1.0 through 1.0.2 by pre-creating the agent's predictable run-folder path hierarchy and Control Interface FIFOs under the shared default location `$TMPDIR/ankaios`. Because the agent reuses an existing directory or FIFO based only on an existence/file-type check — without verifying ownership or permissions — it treats the attacker-owned pipes as the legitimate Control Interface and executes requests under that workload's configured `controlInterfaceAccess` permissions, enabling workload impersonation and unauthorized reading or modification of the cluster's desired state. The flaw is CWE-379 (insecure temporary file/permissions), carries a CVSS 4.0 base score of 8.4 (AV:L/PR:L/AT:P, high confidentiality and integrity impact), and has no public exploit code or CISA KEV listing at time of analysis; EPSS is 0.09%, consistent with a local, non-automatable attack. The vendor released v1.0.3 with an ownership/permission validation check (PR #799).
Incorrect authorization in Eclipse Ankaios v0.5.1-v1.0.1 allows an authenticated workload to bypass its scoped access restrictions on the agent-side Control Interface. When the cluster is configured with multi-segment allow rules whose first path segment is a wildcard (e.g., `*.workloads.some_workload`), submitting a CompleteStateRequest or UpdateStateRequest with an empty field mask is incorrectly evaluated as matching the scoped rule, granting the workload full read or write access beyond its authorized state subtree. No public exploit is identified at time of analysis; a patched release (v1.0.2) is available.
Local attackers holding a low-privileged workload on an Eclipse Ankaios agent can bypass log-access authorization to read other workloads' logs on the same agent. The flaw affects Eclipse Ankaios 0.6.0 through 1.0.3, where the agent's control-interface authorizer stops evaluating a rule at the first wildcard pattern and therefore skips later deny LogRule entries; exploitation requires a rule set in which a wildcard-containing entry precedes a deny rule. This is a low-severity authorization flaw (CVSS 4.8, CWE-863) requiring local access and an existing workload foothold, with no public exploit identified at time of analysis.
Uncontrolled memory allocation in Eclipse Ankaios 0.1.0-1.0.1 allows a workload with granted Control Interface access to abort the agent process by declaring an arbitrarily large protobuf message length over the Control Interface FIFO, causing unbounded heap allocation and an OOM-triggered process crash. The impact is complete loss of orchestration services for all workloads managed by the affected agent instance. No public exploit has been identified and no active exploitation is confirmed; patch v1.0.2 is available.