Vulnerabilities > Linuxfoundation
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2023-09-20 | CVE-2023-43635 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Linuxfoundation Edge Virtualization Engine Vault Key Sealed With SHA1 PCRs The measured boot solution implemented in EVE OS leans on a PCR locking mechanism. Different parts of the system update different PCR values in the TPM, resulting in a unique value for each PCR entry. These PCRs are then used in order to seal/unseal a key from the TPM which is used to encrypt/decrypt the “vault” directory. This “vault” directory is the most sensitive point in the system and as such, its content should be protected. This mechanism is noted in Zededa’s documentation as the “measured boot” mechanism, designed to protect said “vault”. The code that’s responsible for generating and fetching the key from the TPM assumes that SHA256 PCRs are used in order to seal/unseal the key, and as such their presence is being checked. The issue here is that the key is not sealed using SHA256 PCRs, but using SHA1 PCRs. This leads to several issues: • Machines that have their SHA256 PCRs enabled but SHA1 PCRs disabled, as well as not sealing their keys at all, meaning the “vault” is not protected from an attacker. • SHA1 is considered insecure and reduces the complexity level required to unseal the key in machines which have their SHA1 PCRs enabled. An attacker can very easily retrieve the contents of the “vault”, which will effectively render the “measured boot” mechanism meaningless. | 8.8 |
| 2023-09-20 | CVE-2023-43636 | Insufficient Verification of Data Authenticity vulnerability in Linuxfoundation Edge Virtualization Engine In EVE OS, the “measured boot” mechanism prevents a compromised device from accessing the encrypted data located in the vault. As per the “measured boot” design, the PCR values calculated at different stages of the boot process will change if any of their respective parts are changed. This includes, among other things, the configuration of the bios, grub, the kernel cmdline, initrd, and more. However, this mechanism does not validate the entire rootfs, so an attacker can edit the filesystem and gain control over the system. As the default filesystem used by EVE OS is squashfs, this is somewhat harder than an ext4, which is easily changeable. This will not stop an attacker, as an attacker can repackage the squashfs with their changes in it and replace the partition altogether. This can also be done directly on the device, as the “003-storage-init” container contains the “mksquashfs” and “unsquashfs” binaries (with the corresponding libs). An attacker can gain full control over the device without changing the PCR values, thus not triggering the “measured boot” mechanism, and having full access to the vault. Note: This issue was partially fixed in these commits (after disclosure to Zededa), where the config partition measurement was added to PCR13: • aa3501d6c57206ced222c33aea15a9169d629141 • 5fef4d92e75838cc78010edaed5247dfbdae1889. This issue was made viable in version 9.0.0 when the calculation was moved to PCR14 but it was not included in the measured boot. | 8.8 |
| 2023-09-19 | CVE-2022-28357 | Path Traversal vulnerability in Linuxfoundation Nats-Server NATS nats-server 2.2.0 through 2.7.4 allows directory traversal because of an unintended path to a management action from a management account. | 9.8 |
| 2023-09-04 | CVE-2023-20821 | Out-of-bounds Write vulnerability in multiple products In nvram, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2023-09-04 | CVE-2023-20828 | Out-of-bounds Write vulnerability in multiple products In gps, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2023-09-04 | CVE-2023-20829 | Out-of-bounds Write vulnerability in multiple products In gps, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2023-09-04 | CVE-2023-20830 | Out-of-bounds Write vulnerability in multiple products In gps, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2023-09-04 | CVE-2023-20831 | Out-of-bounds Write vulnerability in multiple products In gps, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2023-09-04 | CVE-2023-20832 | Out-of-bounds Write vulnerability in multiple products In gps, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2023-09-04 | CVE-2023-20835 | Use After Free vulnerability in multiple products In camsys, there is a possible use after free due to a race condition. | 6.4 |