Vulnerabilities > Linuxfoundation
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2024-01-03 | CVE-2023-46742 | Unspecified vulnerability in Linuxfoundation Cubefs CubeFS is an open-source cloud-native file storage system. | 6.5 |
| 2024-01-03 | CVE-2023-46738 | Unspecified vulnerability in Linuxfoundation Cubefs CubeFS is an open-source cloud-native file storage system. | 6.5 |
| 2023-12-04 | CVE-2023-32855 | Missing Authorization vulnerability in multiple products In aee, there is a possible escalation of privilege due to a missing permission check. | 6.7 |
| 2023-11-09 | CVE-2023-20902 | Race Condition vulnerability in Linuxfoundation Harbor A timing condition in Harbor 2.6.x and below, Harbor 2.7.2 and below, Harbor 2.8.2 and below, and Harbor 1.10.17 and below allows an attacker with network access to create jobs/stop job tasks and retrieve job task information. | 6.5 |
| 2023-10-30 | CVE-2023-47090 | Incorrect Authorization vulnerability in Linuxfoundation Nats-Server NATS nats-server before 2.9.23 and 2.10.x before 2.10.2 has an authentication bypass. | 6.5 |
| 2023-10-02 | CVE-2023-32820 | Reachable Assertion vulnerability in multiple products In wlan firmware, there is a possible firmware assertion due to improper input handling. | 7.5 |
| 2023-10-02 | CVE-2023-32829 | Integer Overflow or Wraparound vulnerability in multiple products In apusys, there is a possible out of bounds write due to an integer overflow. | 6.7 |
| 2023-09-21 | CVE-2023-43631 | Insufficiently Protected Credentials vulnerability in Linuxfoundation Edge Virtualization Engine On boot, the Pillar eve container checks for the existence and content of “/config/authorized_keys”. If the file is present, and contains a supported public key, the container will go on to open port 22 and enable sshd with the given keys as the authorized keys for root login. An attacker could easily add their own keys and gain full control over the system without triggering the “measured boot” mechanism implemented by EVE OS, and without marking the device as “UUD” (“Unknown Update Detected”). This is because the “/config” partition is not protected by “measured boot”, it is mutable, and it is not encrypted in any way. 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-21 | CVE-2023-43632 | Allocation of Resources Without Limits or Throttling vulnerability in Linuxfoundation Edge Virtualization Engine As noted in the “VTPM.md” file in the eve documentation, “VTPM is a server listening on port 8877 in EVE, exposing limited functionality of the TPM to the clients. | 9.9 |
| 2023-09-20 | CVE-2023-43630 | Insufficiently Protected Credentials vulnerability in Linuxfoundation Edge Virtualization Engine PCR14 is not in the list of PCRs that seal/unseal the “vault” key, but due to the change that was implemented in commit “7638364bc0acf8b5c481b5ce5fea11ad44ad7fd4”, fixing this issue alone would not solve the problem of the config partition not being measured correctly. Also, the “vault” key is sealed/unsealed with SHA1 PCRs instead of SHA256. | 8.8 |