There are 9 open security issues in bullseye.
8 issues left for the package maintainer to handle:
- CVE-2022-2347:
(needs triaging)
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-2021-27097:
(needs triaging)
The boot loader in Das U-Boot before 2021.04-rc2 mishandles a modified FIT.
- CVE-2021-27138:
(needs triaging)
The boot loader in Das U-Boot before 2021.04-rc2 mishandles use of unit addresses in a FIT.
- CVE-2022-30552:
(needs triaging)
Das U-Boot 2022.01 has a Buffer Overflow.
- CVE-2022-30790:
(needs triaging)
Das U-Boot 2022.01 has a Buffer Overflow, a different issue than CVE-2022-30552.
- CVE-2022-33103:
(needs triaging)
Das U-Boot from v2020.10 to v2022.07-rc3 was discovered to contain an out-of-bounds write via the function sqfs_readdir().
- CVE-2022-33967:
(needs triaging)
squashfs filesystem implementation of U-Boot versions from v2020.10-rc2 to v2022.07-rc5 contains a heap-based buffer overflow vulnerability due to a defect in the metadata reading process. Loading a specially crafted squashfs image may lead to a denial-of-service (DoS) condition or arbitrary code execution.
- CVE-2022-34835:
(needs triaging)
In Das U-Boot through 2022.07-rc5, an integer signedness error and resultant stack-based buffer overflow in the "i2c md" command enables the corruption of the return address pointer of the do_i2c_md function.
You can find information about how to handle these issues in the security team's documentation.
1 ignored issue:
- CVE-2022-30767:
nfs_lookup_reply in net/nfs.c in Das U-Boot through 2022.04 (and through 2022.07-rc2) has an unbounded memcpy with a failed length check, leading to a buffer overflow. NOTE: this issue exists because of an incorrect fix for CVE-2019-14196.