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 |