Filtered by vendor Zephyrproject
Subscribe
Total
104 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2022-2993 | 1 Zephyrproject | 1 Zephyr | 2025-04-22 | N/A | 8.6 HIGH |
| 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-2023-0396 | 1 Zephyrproject | 1 Zephyr | 2025-04-03 | N/A | 6.8 MEDIUM |
| A malicious / defective bluetooth controller can cause buffer overreads in the most functions that process HCI command responses. | |||||
| CVE-2022-3806 | 1 Zephyrproject | 1 Zephyr | 2025-04-03 | N/A | 9.8 CRITICAL |
| Inconsistent handling of error cases in bluetooth hci may lead to a double free condition of a network buffer. | |||||
| CVE-2023-7060 | 1 Zephyrproject | 1 Zephyr | 2025-03-27 | N/A | 8.6 HIGH |
| Zephyr OS IP packet handling does not properly drop IP packets arriving on an external interface with a source address equal to 127.0.01 or the destination address. | |||||
| CVE-2025-1674 | 1 Zephyrproject | 1 Zephyr | 2025-02-28 | N/A | 8.2 HIGH |
| A lack of input validation allows for out of bounds reads caused by malicious or malformed packets. | |||||
| CVE-2025-1673 | 1 Zephyrproject | 1 Zephyr | 2025-02-28 | N/A | 8.2 HIGH |
| A malicious or malformed DNS packet without a payload can cause an out-of-bounds read, resulting in a crash (denial of service) or an incorrect computation. | |||||
| CVE-2023-5753 | 1 Zephyrproject | 1 Zephyr | 2025-02-13 | N/A | 6.3 MEDIUM |
| Potential buffer overflows in the Bluetooth subsystem due to asserts being disabled in /subsys/bluetooth/host/hci_core.c | |||||
| CVE-2023-5184 | 1 Zephyrproject | 1 Zephyr | 2025-02-13 | N/A | 7.0 HIGH |
| Two potential signed to unsigned conversion errors and buffer overflow vulnerabilities at the following locations in the Zephyr IPM drivers. | |||||
| CVE-2023-4264 | 1 Zephyrproject | 1 Zephyr | 2025-02-13 | N/A | 7.1 HIGH |
| Potential buffer overflow vulnerabilities n the Zephyr Bluetooth subsystem. | |||||
| CVE-2023-4260 | 1 Zephyrproject | 1 Zephyr | 2025-02-13 | N/A | 6.3 MEDIUM |
| Potential off-by-one buffer overflow vulnerability in the Zephyr fuse file system. | |||||
| CVE-2024-4785 | 1 Zephyrproject | 1 Zephyr | 2025-02-03 | N/A | 7.6 HIGH |
| BT: Missing Check in LL_CONNECTION_UPDATE_IND Packet Leads to Division by Zero | |||||
| CVE-2024-8798 | 1 Zephyrproject | 1 Zephyr | 2025-02-03 | N/A | 7.5 HIGH |
| No proper validation of the length of user input in olcp_ind_handler in zephyr/subsys/bluetooth/services/ots/ots_client.c. | |||||
| CVE-2024-11263 | 1 Zephyrproject | 1 Zephyr | 2025-02-03 | N/A | 9.3 CRITICAL |
| When the Global Pointer (GP) relative addressing is enabled (CONFIG_RISCV_GP=y), the gp reg points at 0x800 bytes past the start of the .sdata section which is then used by the linker to relax accesses to global symbols. | |||||
| CVE-2024-3332 | 1 Zephyrproject | 1 Zephyr | 2025-02-03 | N/A | 6.5 MEDIUM |
| A malicious BLE device can send a specific order of packet sequence to cause a DoS attack on the victim BLE device | |||||
| 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. | |||||