Filtered by vendor Zephyrproject
Subscribe
Total
105 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2024-3077 | 1 Zephyrproject | 1 Zephyr | 2025-01-23 | N/A | 6.8 MEDIUM |
An malicious BLE device can crash BLE victim device by sending malformed gatt packet | |||||
CVE-2023-6881 | 1 Zephyrproject | 1 Zephyr | 2025-01-23 | N/A | 7.3 HIGH |
Possible buffer overflow in is_mount_point | |||||
CVE-2023-6249 | 1 Zephyrproject | 1 Zephyr | 2025-01-23 | N/A | 8.0 HIGH |
Signed to unsigned conversion esp32_ipm_send | |||||
CVE-2023-5779 | 1 Zephyrproject | 1 Zephyr | 2025-01-22 | N/A | 4.4 MEDIUM |
can: out of bounds in remove_rx_filter function | |||||
CVE-2023-6749 | 1 Zephyrproject | 1 Zephyr | 2025-01-22 | N/A | 8.0 HIGH |
Unchecked length coming from user input in settings shell | |||||
CVE-2024-1638 | 1 Zephyrproject | 1 Zephyr | 2025-01-17 | N/A | 8.2 HIGH |
The documentation specifies that the BT_GATT_PERM_READ_LESC and BT_GATT_PERM_WRITE_LESC defines for a Bluetooth characteristic: Attribute read/write permission with LE Secure Connection encryption. If set, requires that LE Secure Connections is used for read/write access, however this is only true when it is combined with other permissions, namely BT_GATT_PERM_READ_ENCRYPT/BT_GATT_PERM_READ_AUTHEN (for read) or BT_GATT_PERM_WRITE_ENCRYPT/BT_GATT_PERM_WRITE_AUTHEN (for write), if these additional permissions are not set (even in secure connections only mode) then the stack does not perform any permission checks on these characteristics and they can be freely written/read. | |||||
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. |