Filtered by vendor Zephyrproject
Subscribe
Total
104 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2023-5563 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 7.1 HIGH |
The SJA1000 CAN controller driver backend automatically attempt to recover from a bus-off event when built with CONFIG_CAN_AUTO_BUS_OFF_RECOVERY=y. This results in calling k_sleep() in IRQ context, causing a fatal exception. | |||||
CVE-2023-5139 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 4.4 MEDIUM |
Potential buffer overflow vulnerability at the following location in the Zephyr STM32 Crypto driver | |||||
CVE-2023-5055 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 8.3 HIGH |
Possible variant of CVE-2021-3434 in function le_ecred_reconf_req. | |||||
CVE-2023-4424 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 8.3 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-4265 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 6.4 MEDIUM |
Potential buffer overflow vulnerabilities in the following locations: https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/usb/device/usb_dc_native_posix.c#L359 https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/usb/device/usb_dc_native_posix.c#L359 https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/usb/device/class/netusb/function_rndis... https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/usb/device/class/netusb/function_rndis.c#L841 | |||||
CVE-2023-4263 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 7.6 HIGH |
Potential buffer overflow vulnerability in the Zephyr IEEE 802.15.4 nRF 15.4 driver | |||||
CVE-2023-4259 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 7.1 HIGH |
Two potential buffer overflow vulnerabilities at the following locations in the Zephyr eS-WiFi driver source code. | |||||
CVE-2023-4258 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 8.6 HIGH |
In Bluetooth mesh implementation If provisionee has a public key that is sent OOB then during provisioning it can be sent back and will be accepted by provisionee. | |||||
CVE-2023-4257 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 7.6 HIGH |
Unchecked user input length in /subsys/net/l2/wifi/wifi_shell.c can cause buffer overflows. | |||||
CVE-2023-3725 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 7.6 HIGH |
Potential buffer overflow vulnerability in the Zephyr CAN bus subsystem | |||||
CVE-2023-2234 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 6.8 MEDIUM |
Union variant confusion allows any malicious BT controller to execute arbitrary code on the Zephyr host. | |||||
CVE-2023-1902 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 5.9 MEDIUM |
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-1901 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 5.9 MEDIUM |
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-11-21 | N/A | 6.7 MEDIUM |
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-2023-0397 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 9.6 CRITICAL |
A malicious / defect bluetooth controller can cause a Denial of Service due to unchecked input in le_read_buffer_size_complete. | |||||
CVE-2023-0359 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 5.9 MEDIUM |
A missing nullptr-check in handle_ra_input can cause a nullptr-deref. | |||||
CVE-2022-2741 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 8.2 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). | |||||
CVE-2022-1841 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 7.2 HIGH |
In subsys/net/ip/tcp.c , function tcp_flags , when the incoming parameter flags is ECN or CWR , the buf will out-of-bounds write a byte zero. | |||||
CVE-2022-1042 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 8.2 HIGH |
In Zephyr bluetooth mesh core stack, an out-of-bound write vulnerability can be triggered during provisioning. | |||||
CVE-2022-1041 | 1 Zephyrproject | 1 Zephyr | 2024-11-21 | N/A | 8.2 HIGH |
In Zephyr bluetooth mesh core stack, an out-of-bound write vulnerability can be triggered during provisioning. |