Vulnerabilities (CVE)

Filtered by vendor Pengutronix Subscribe
Filtered by product Barebox
Total 6 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2026-33243 2 Denx, Pengutronix 2 U-boot, Barebox 2026-03-26 N/A 8.2 HIGH
barebox is a bootloader. In barebox from version 2016.03.0 to before version 2026.03.1 (and the corresponding backport to 2025.09.3), an attacker could exploit a FIT signature verification vulnerability to trick the bootloader into booting different images than those that were verified as part of a signed configuration. mkimage(1) sets the hashed-nodes property of the FIT signature node to list which nodes of the FIT were hashed as part of the signing process as these will need to be verified later on by the bootloader. However, hashed-nodes itself is not part of the hash and could therefore be modified to allow booting different images than those that have been verified. This issue has been patched in barebox versions 2026.03.1 and backported to 2025.09.3.
CVE-2021-37848 1 Pengutronix 1 Barebox 2024-11-21 5.0 MEDIUM 7.5 HIGH
common/password.c in Pengutronix barebox through 2021.07.0 leaks timing information because strncmp is used during hash comparison.
CVE-2021-37847 1 Pengutronix 1 Barebox 2024-11-21 5.0 MEDIUM 7.5 HIGH
crypto/digest.c in Pengutronix barebox through 2021.07.0 leaks timing information because memcmp is used during digest verification.
CVE-2020-13910 1 Pengutronix 1 Barebox 2024-11-21 6.4 MEDIUM 9.1 CRITICAL
Pengutronix Barebox through v2020.05.0 has an out-of-bounds read in nfs_read_reply in net/nfs.c because a field of an incoming network packet is directly used as a length field without any bounds check.
CVE-2019-15938 1 Pengutronix 1 Barebox 2024-11-21 7.5 HIGH 9.8 CRITICAL
Pengutronix barebox through 2019.08.1 has a remote buffer overflow in nfs_readlink_req in fs/nfs.c because a length field is directly used for a memcpy.
CVE-2019-15937 1 Pengutronix 1 Barebox 2024-11-21 7.5 HIGH 9.8 CRITICAL
Pengutronix barebox through 2019.08.1 has a remote buffer overflow in nfs_readlink_reply in net/nfs.c because a length field is directly used for a memcpy.