Threat database

Contrast versions from 1.8.0 up to but not including 1.24.1 contain a vulnerability in the Coordinator peer recovery process where data authenticity verification is insufficient. This flaw allows attackers with write access to the manifest history to replay outdated manifest states, enabling withdrawn workloads to receive trusted mesh certificates. Additionally, if the attacker has access to the secret seed, they can disclose the Mesh CA key. The vulnerability has a high severity score of 8.7 CVSS 4.0.

Edgeless Systems Contrast versions 1.8.0 up to but not including 1.24.1 have an incorrect permission assignment vulnerability. The node installer sets the containerd configuration file to be world-writable (0666), allowing local unprivileged users to modify it. This can lead to privilege escalation by overwriting critical configuration such as the runc binary location.

Edgelesssys Contrast is a confidential-computing runtime for Kubernetes. In versions 1.9.0 before 1.12.2, the initializer logs the full NewMeshCert response — which contains the workload secret — to standard output at INFO level. As a result, workload secrets are exposed to any Kubernetes user with get or list permission on pods/logs. Because workload secrets are used for encrypted storage and Vault integration, those must also be considered compromised. This is a regression of GHSA-h5f8-crrq-4pw8.

Constellation is the first Confidential Kubernetes. The Constellation CVM image uses LUKS2-encrypted volumes for persistent storage. When opening an encrypted storage device, the CVM uses the libcryptsetup function crypt_activate_by_passhrase. If the VM is successful in opening the partition with the disk encryption key, it treats the volume as confidential. However, due to the unsafe handling of null keyslot algorithms in the cryptsetup 2.8.1, it is possible that the opened volume is not encrypted at all. Cryptsetup prior to version 2.8.1 does not report an error when processing LUKS2-formatted disks that use the cipher_null-ecb algorithm in the keyslot encryption field. This vulnerability is fixed in 2.24.0.