Filtered by vendor Zephyrproject
Subscribe
Total
75 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2023-5055 | 1 Zephyrproject | 1 Zephyr | 2024-02-05 | N/A | 9.8 CRITICAL |
| Possible variant of CVE-2021-3434 in function le_ecred_reconf_req. | |||||
| CVE-2023-4424 | 1 Zephyrproject | 1 Zephyr | 2024-02-05 | N/A | 8.8 HIGH |
| An malicious BLE device can cause buffer overflow by sending malformed advertising packet BLE device using Zephyr OS, leading to DoS or potential RCE on the victim BLE device. | |||||
| CVE-2023-5139 | 1 Zephyrproject | 1 Zephyr | 2024-02-05 | N/A | 7.8 HIGH |
| Potential buffer overflow vulnerability at the following location in the Zephyr STM32 Crypto driver | |||||
| CVE-2023-5184 | 1 Zephyrproject | 1 Zephyr | 2024-02-05 | N/A | 8.8 HIGH |
| Two potential signed to unsigned conversion errors and buffer overflow vulnerabilities at the following locations in the Zephyr IPM drivers. | |||||
| CVE-2023-4259 | 1 Zephyrproject | 1 Zephyr | 2024-02-05 | N/A | 8.8 HIGH |
| Two potential buffer overflow vulnerabilities at the following locations in the Zephyr eS-WiFi driver source code. | |||||
| CVE-2023-3725 | 1 Zephyrproject | 1 Zephyr | 2024-02-05 | N/A | 9.8 CRITICAL |
| Potential buffer overflow vulnerability in the Zephyr CAN bus subsystem | |||||
| CVE-2023-4264 | 1 Zephyrproject | 1 Zephyr | 2024-02-05 | N/A | 9.6 CRITICAL |
| Potential buffer overflow vulnerabilities n the Zephyr Bluetooth subsystem. | |||||
| CVE-2023-4263 | 1 Zephyrproject | 1 Zephyr | 2024-02-05 | N/A | 8.8 HIGH |
| Potential buffer overflow vulnerability in the Zephyr IEEE 802.15.4 nRF 15.4 driver | |||||
| CVE-2023-4260 | 1 Zephyrproject | 1 Zephyr | 2024-02-05 | N/A | 10.0 CRITICAL |
| Potential off-by-one buffer overflow vulnerability in the Zephyr fuse file system. | |||||
| CVE-2023-4262 | 1 Zephyrproject | 1 Zephyr | 2024-02-05 | N/A | 10.0 CRITICAL |
| Possible buffer overflow in Zephyr mgmt subsystem when asserts are disabled | |||||
| CVE-2023-1902 | 1 Zephyrproject | 1 Zephyr | 2024-02-04 | N/A | 8.0 HIGH |
| The bluetooth HCI host layer logic not clearing a global reference to a state pointer after handling connection events may allow a malicious HCI Controller to cause the use of a dangling reference in the host layer, leading to a crash (DoS) or potential RCE on the Host layer. | |||||
| CVE-2023-2234 | 1 Zephyrproject | 1 Zephyr | 2024-02-04 | N/A | 8.8 HIGH |
| Union variant confusion allows any malicious BT controller to execute arbitrary code on the Zephyr host. | |||||
| CVE-2023-0359 | 1 Zephyrproject | 1 Zephyr | 2024-02-04 | N/A | 7.5 HIGH |
| A missing nullptr-check in handle_ra_input can cause a nullptr-deref. | |||||
| CVE-2023-1901 | 1 Zephyrproject | 1 Zephyr | 2024-02-04 | N/A | 8.0 HIGH |
| The bluetooth HCI host layer logic not clearing a global reference to a semaphore after synchronously sending HCI commands may allow a malicious HCI Controller to cause the use of a dangling reference in the host layer, leading to a crash (DoS) or potential RCE on the Host layer. | |||||
| CVE-2023-0779 | 1 Zephyrproject | 1 Zephyr | 2024-02-04 | N/A | 7.7 HIGH |
| At the most basic level, an invalid pointer can be input that crashes the device, but with more knowledge of the device’s memory layout, further exploitation is possible. | |||||
| CVE-2022-2993 | 1 Zephyrproject | 1 Zephyr | 2024-02-04 | N/A | 9.8 CRITICAL |
| There is an error in the condition of the last if-statement in the function smp_check_keys. It was rejecting current keys if all requirements were unmet. | |||||
| CVE-2021-3329 | 1 Zephyrproject | 1 Zephyr | 2024-02-04 | N/A | 6.5 MEDIUM |
| Lack of proper validation in HCI Host stack initialization can cause a crash of the bluetooth stack | |||||
| CVE-2022-0553 | 1 Zephyrproject | 1 Zephyr | 2024-02-04 | N/A | 4.6 MEDIUM |
| There is no check to see if slot 0 is being uploaded from the device to the host. When using encrypted images this means the unencrypted firmware can be retrieved easily. | |||||
| CVE-2022-1041 | 1 Zephyrproject | 1 Zephyr | 2024-02-04 | N/A | 8.8 HIGH |
| In Zephyr bluetooth mesh core stack, an out-of-bound write vulnerability can be triggered during provisioning. | |||||
| CVE-2022-2741 | 1 Zephyrproject | 1 Zephyr | 2024-02-04 | N/A | 7.5 HIGH |
| The denial-of-service can be triggered by transmitting a carefully crafted CAN frame on the same CAN network as the vulnerable node. The frame must have a CAN ID matching an installed filter in the vulnerable node (this can easily be guessed based on CAN traffic analyses). The frame must contain the opposite RTR bit as what the filter installed in the vulnerable node contains (if the filter matches RTR frames, the frame must be a data frame or vice versa). | |||||