CPE Details
Zephyrproject Zephyr 2.5.1 Release Candidate 1
2.5.1
2021-10-12
13h59 +00:00
13h59 +00:00
2021-10-12
14h23 +00:00
14h23 +00:00
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
CPE Name: cpe:2.3:o:zephyrproject:zephyr:2.5.1:rc1:*:*:*:*:*:*
Informations
Vendor
zephyrprojectProduct
zephyrVersion
2.5.1Update
rc1Related CVE
| CVE ID | Publié | Description | Score | Gravité |
|---|---|---|---|---|
| A lack of input validation allows for out of bounds reads caused by malicious or malformed packets. | 8.2 |
Haute |
||
| 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. | 8.2 |
Haute |
||
| No proper validation of the length of user input in olcp_ind_handler in zephyr/subsys/bluetooth/services/ots/ots_client.c. | 7.5 |
Haute |
||
| 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. | 9.4 |
Critique |
||
| No proper validation of the length of user input in olcp_ind_handler in zephyr/subsys/bluetooth/services/ots/ots_client.c. | 6.5 |
Moyen |
||
| In utf8_trunc in zephyr/lib/utils/utf8.c, last_byte_p can point to one byte before the string pointer if the string is empty. | 6.5 |
Moyen |
||
| In ascs_cp_rsp_add in /subsys/bluetooth/audio/ascs.c, an unchecked tailroom could lead to a global buffer overflow. | 6.5 |
Moyen |
||
| BT: HCI: adv_ext_report Improper discarding in adv_ext_report | 7.6 |
Haute |
||
| BT: Classic: SDP OOB access in get_att_search_list | 7.6 |
Haute |
||
| BT:Classic: Multiple missing buf length checks | 7.6 |
Haute |
||
| BT: Unchecked user input in bap_broadcast_assistant | 6.5 |
Moyen |
||
| BT: Missing length checks of net_buf in rfcomm_handle_data | 6.8 |
Moyen |
||
| BT: Encryption procedure host vulnerability | 8.2 |
Haute |
||
| BT: Missing Check in LL_CONNECTION_UPDATE_IND Packet Leads to Division by Zero | 7.6 |
Haute |
||
| A malicious BLE device can send a specific order of packet sequence to cause a DoS attack on the victim BLE device | 6.5 |
Moyen |
||
| An malicious BLE device can crash BLE victim device by sending malformed gatt packet | 6.8 |
Moyen |
||
| 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. | 8.6 |
Haute |
||
| Possible buffer overflow in is_mount_point | 9.8 |
Critique |
||
| 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. | 9.1 |
Critique |
||
| can: out of bounds in remove_rx_filter function | 9.8 |
Critique |
||
| Signed to unsigned conversion esp32_ipm_send | 9.8 |
Critique |
||
| Unchecked length coming from user input in settings shell | 9.8 |
Critique |
||
| Possible variant of CVE-2021-3434 in function le_ecred_reconf_req. | 9.8 |
Critique |
||
| 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. | 8.8 |
Haute |
||
| Potential buffer overflow vulnerability at the following location in the Zephyr STM32 Crypto driver | 7.8 |
Haute |
||
| Potential buffer overflows in the Bluetooth subsystem due to asserts being disabled in /subsys/bluetooth/host/hci_core.c | 8.8 |
Haute |
||
| Unchecked user input length in /subsys/net/l2/wifi/wifi_shell.c can cause buffer overflows. | 9.8 |
Critique |
||
| Potential buffer overflow vulnerability in the Zephyr IEEE 802.15.4 nRF 15.4 driver | 8.8 |
Haute |
||
| 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. | 7.5 |
Haute |
||
| Potential buffer overflow vulnerability in the Zephyr CAN bus subsystem | 9.8 |
Critique |
||
| Two potential signed to unsigned conversion errors and buffer overflow vulnerabilities at the following locations in the Zephyr IPM drivers. | 8.8 |
Haute |
||
| Potential off-by-one buffer overflow vulnerability in the Zephyr fuse file system. | 10 |
Critique |
||
| Potential buffer overflow vulnerabilities n the Zephyr Bluetooth subsystem. | 9.6 |
Critique |
||
| Two potential buffer overflow vulnerabilities at the following locations in the Zephyr eS-WiFi driver source code. | 8.8 |
Haute |
||
| 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. | 8.6 |
Haute |
||
| 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 | 6.8 |
Moyen |
||
| 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. | 8 |
Haute |
||
| Union variant confusion allows any malicious BT controller to execute arbitrary code on the Zephyr host. | 8.8 |
Haute |
||
| 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. | 8 |
Haute |
||
| A missing nullptr-check in handle_ra_input can cause a nullptr-deref. | 7.5 |
Haute |
||
| 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. | 7.7 |
Haute |
||
| Inconsistent handling of error cases in bluetooth hci may lead to a double free condition of a network buffer. | 9.8 |
Critique |
||
| A malicious / defective bluetooth controller can cause buffer overreads in the most functions that process HCI command responses. | 6.8 |
Moyen |
||
| A malicious / defect bluetooth controller can cause a Denial of Service due to unchecked input in le_read_buffer_size_complete. | 9.6 |
Critique |
||
| usb device bluetooth class includes a buffer overflow related to implementation of net_buf_add_mem. | 9.6 |
Critique |
||
| 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. | 6.5 |
Moyen |
||
| 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. | 9.8 |
Critique |
||
| 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). | 8.2 |
Haute |
||
| 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. | 7.2 |
Haute |
||
| In Zephyr bluetooth mesh core stack, an out-of-bound write vulnerability can be triggered during provisioning. | 8.8 |
Haute |
||
| In Zephyr bluetooth mesh core stack, an out-of-bound write vulnerability can be triggered during provisioning. | 8.8 |
Haute |
||
| 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 | 4 |
Moyen |
||
| Stack based buffer overflow in le_ecred_conn_req(). Zephyr versions >= v2.5.0 Stack-based Buffer Overflow (CWE-121). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-8w87-6rfp-cfrm | 7.8 |
Haute |
||
| 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 | 4 |
Moyen |
||
| 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 | 7.5 |
Haute |
||
| Assertion reachable with repeated LL_FEATURE_REQ. Zephyr versions >= v2.5.0 contain Reachable Assertion (CWE-617). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-7548-5m6f-mqv9 | 7.5 |
Haute |
||
| 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 | 7.5 |
Haute |
||
| Truncated L2CAP K-frame causes assertion failure. Zephyr versions >= 2.4.0, >= v.2.50 contain Improper Handling of Length Parameter Inconsistency (CWE-130), Reachable Assertion (CWE-617). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-fx88-6c29-vrp3 | 7.5 |
Haute |
||
| Disconnecting L2CAP channel right after invalid ATT request leads freeze. Zephyr versions >= 2.4.0, >= 2.5.0 contain Use After Free (CWE-416). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-7g38-3x9v-v7vp | 7.5 |
Haute |
||
| Buffer overflow in Zephyr USB DFU DNLOAD. Zephyr versions >= v2.5.0 contain Heap-based Buffer Overflow (CWE-122). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-c3gr-hgvr-f363 | 9.8 |
Critique |
||
| Buffer Access with Incorrect Length Value in zephyr. Zephyr versions >= >=2.5.0 contain Buffer Access with Incorrect Length Value (CWE-805). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-8q65-5gqf-fmw5 | 8.8 |
Haute |
||
| Zephyr JSON decoder incorrectly decodes array of array. Zephyr versions >= >1.14.0, >= >2.5.0 contain Attempt to Access Child of a Non-structure Pointer (CWE-588). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-289f-7mw3-2qf4 | 7.5 |
Haute |
