Filtered by vendor Zephyrproject
Subscribe
Total
88 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2023-4260 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | N/A | 10.0 CRITICAL |
Potential off-by-one buffer overflow vulnerability in the Zephyr fuse file system. | |||||
CVE-2023-4265 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | N/A | 6.8 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-2234 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | 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-28 | N/A | 7.5 HIGH |
A missing nullptr-check in handle_ra_input can cause a nullptr-deref. | |||||
CVE-2023-0779 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | 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-28 | 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-2023-0397 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | N/A | 6.5 MEDIUM |
A malicious / defect bluetooth controller can cause a Denial of Service due to unchecked input in le_read_buffer_size_complete. | |||||
CVE-2022-0553 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | 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-3806 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | 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-0396 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | N/A | 6.8 MEDIUM |
A malicious / defective bluetooth controller can cause buffer overreads in the most functions that process HCI command responses. | |||||
CVE-2021-3966 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | N/A | 8.8 HIGH |
usb device bluetooth class includes a buffer overflow related to implementation of net_buf_add_mem. | |||||
CVE-2021-3329 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | N/A | 6.5 MEDIUM |
Lack of proper validation in HCI Host stack initialization can cause a crash of the bluetooth stack | |||||
CVE-2022-1041 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | N/A | 8.8 HIGH |
In Zephyr bluetooth mesh core stack, an out-of-bound write vulnerability can be triggered during provisioning. | |||||
CVE-2022-1042 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | N/A | 8.8 HIGH |
In Zephyr bluetooth mesh core stack, an out-of-bound write vulnerability can be triggered during provisioning. | |||||
CVE-2022-1841 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | N/A | 5.3 MEDIUM |
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-2741 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | 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). | |||||
CVE-2021-3435 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | 2.1 LOW | 3.3 LOW |
Information leakage in le_ecred_conn_req(). Zephyr versions >= v2.4.0 Use of Uninitialized Resource (CWE-908). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-xhg3-gvj6-4rqh | |||||
CVE-2021-3432 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | 5.0 MEDIUM | 7.5 HIGH |
Invalid interval in CONNECT_IND leads to Division by Zero. Zephyr versions >= v1.14.0 Divide By Zero (CWE-369). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-7364-p4wc-8mj4 | |||||
CVE-2021-3433 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | 2.1 LOW | 3.3 LOW |
Invalid channel map in CONNECT_IND results to Deadlock. Zephyr versions >= v2.5.0 Improper Check or Handling of Exceptional Conditions (CWE-703). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-3c2f-w4v6-qxrp | |||||
CVE-2021-3430 | 1 Zephyrproject | 1 Zephyr | 2024-02-28 | 5.0 MEDIUM | 7.5 HIGH |
Assertion reachable with repeated LL_CONNECTION_PARAM_REQ. Zephyr versions >= v1.14 contain Reachable Assertion (CWE-617). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-46h3-hjcq-2jjr |