Filtered by vendor Denx
Subscriptions
Total
36 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2018-1000205 | 1 Denx | 1 U-boot | 2024-09-17 | 5.5 Medium |
| U-Boot contains a CWE-20: Improper Input Validation vulnerability in Verified boot signature validation that can result in Bypass verified boot. This attack appear to be exploitable via Specially crafted FIT image and special device memory functionality. | ||||
| CVE-2022-2347 | 1 Denx | 1 U-boot | 2024-09-16 | 7.7 High |
| There exists an unchecked length field in UBoot. The U-Boot DFU implementation does not bound the length field in USB DFU download setup packets, and it does not verify that the transfer direction corresponds to the specified command. Consequently, if a physical attacker crafts a USB DFU download setup packet with a `wLength` greater than 4096 bytes, they can write beyond the heap-allocated request buffer. | ||||
| CVE-2017-3226 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| Das U-Boot is a device bootloader that can read its configuration from an AES encrypted file. Devices that make use of Das U-Boot's AES-CBC encryption feature using environment encryption (i.e., setting the configuration parameter CONFIG_ENV_AES=y) read environment variables from disk as the encrypted disk image is processed. An attacker with physical access to the device can manipulate the encrypted environment data to include a crafted two-byte sequence which triggers an error in environment variable parsing. This error condition is improperly handled by Das U-Boot, resulting in an immediate process termination with a debugging message. | ||||
| CVE-2017-3225 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| Das U-Boot is a device bootloader that can read its configuration from an AES encrypted file. For devices utilizing this environment encryption mode, U-Boot's use of a zero initialization vector may allow attacks against the underlying cryptographic implementation and allow an attacker to decrypt the data. Das U-Boot's AES-CBC encryption feature uses a zero (0) initialization vector. This allows an attacker to perform dictionary attacks on encrypted data produced by Das U-Boot to learn information about the encrypted data. | ||||
| CVE-2018-18439 | 1 Denx | 1 U-boot | 2024-08-05 | 9.8 Critical |
| DENX U-Boot through 2018.09-rc1 has a remotely exploitable buffer overflow via a malicious TFTP server because TFTP traffic is mishandled. Also, local exploitation can occur via a crafted kernel image. | ||||
| CVE-2018-18440 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| DENX U-Boot through 2018.09-rc1 has a locally exploitable buffer overflow via a crafted kernel image because filesystem loading is mishandled. | ||||
| CVE-2018-3968 | 1 Denx | 1 U-boot | 2024-08-05 | 7.0 High |
| An exploitable vulnerability exists in the verified boot protection of the Das U-Boot from version 2013.07-rc1 to 2014.07-rc2. The affected versions lack proper FIT signature enforcement, which allows an attacker to bypass U-Boot's verified boot and execute an unsigned kernel, embedded in a legacy image format. To trigger this vulnerability, a local attacker needs to be able to supply the image to boot. | ||||
| CVE-2019-14203 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is a stack-based buffer overflow in this nfs_handler reply helper function: nfs_mount_reply. | ||||
| CVE-2019-14194 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is an unbounded memcpy with a failed length check at nfs_read_reply when calling store_block in the NFSv2 case. | ||||
| CVE-2019-14192 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is an unbounded memcpy when parsing a UDP packet due to a net_process_received_packet integer underflow during an nc_input_packet call. | ||||
| CVE-2019-14196 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is an unbounded memcpy with a failed length check at nfs_lookup_reply. | ||||
| CVE-2019-14198 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is an unbounded memcpy with a failed length check at nfs_read_reply when calling store_block in the NFSv3 case. | ||||
| CVE-2019-14202 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is a stack-based buffer overflow in this nfs_handler reply helper function: nfs_readlink_reply. | ||||
| CVE-2019-14199 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is an unbounded memcpy when parsing a UDP packet due to a net_process_received_packet integer underflow during an *udp_packet_handler call. | ||||
| CVE-2019-14193 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is an unbounded memcpy with an unvalidated length at nfs_readlink_reply, in the "if" block after calculating the new path length. | ||||
| CVE-2019-14200 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is a stack-based buffer overflow in this nfs_handler reply helper function: rpc_lookup_reply. | ||||
| CVE-2019-14195 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is an unbounded memcpy with unvalidated length at nfs_readlink_reply in the "else" block after calculating the new path length. | ||||
| CVE-2019-14204 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is a stack-based buffer overflow in this nfs_handler reply helper function: nfs_umountall_reply. | ||||
| CVE-2019-14197 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is a read of out-of-bounds data at nfs_read_reply. | ||||
| CVE-2019-14201 | 1 Denx | 1 U-boot | 2024-08-05 | N/A |
| An issue was discovered in Das U-Boot through 2019.07. There is a stack-based buffer overflow in this nfs_handler reply helper function: nfs_lookup_reply. | ||||