7 matches found
U-Boot tools: double free vulnerability
Background U-Boot tools provides utiiities for working with Das U-Boot. Description A vulnerability has been discovered in U-Boot tools. Please review the CVE identifier referenced below for details. Impact In Das U-Boot a double free has been found in the cmd/gpt.c dorenamegptparts function...
CVE-2020-8432
In Das U-Boot through 2020.01, a double free has been found in the cmd/gpt.c dorenamegptparts function. Double freeing may result in a write-what-where condition, allowing an attacker to execute arbitrary code. NOTE: this vulnerablity was introduced when attempting to fix a memory leak identified...
CVE-2020-8432
In Das U-Boot through 2020.01, a double free has been found in the cmd/gpt.c dorenamegptparts function. Double freeing may result in a write-what-where condition, allowing an attacker to execute arbitrary code. NOTE: this vulnerablity was introduced when attempting to fix a memory leak identified...
CVE-2020-8432
In Das U-Boot through 2020.01, a double free has been found in the cmd/gpt.c dorenamegptparts function. Double freeing may result in a write-what-where condition, allowing an attacker to execute arbitrary code. NOTE: this vulnerablity was introduced when attempting to fix a memory leak identified...
CVE-2020-8432
CVE-2020-8432 affects Das U-Boot up to 2020.01, with a double free in the cmd/gpt.c do_rename_gpt_parts() function. The double free can lead to a write-what-where condition and remote code execution. The issue was introduced during a memory-leak fix identified by static analysis. Publicly referen...
CVE-2020-8432
In Das U-Boot through 2020.01, a double free has been found in the cmd/gpt.c dorenamegptparts function. Double freeing may result in a write-what-where condition, allowing an attacker to execute arbitrary code. NOTE: this vulnerablity was introduced when attempting to fix a memory leak identified...
CVE-2020-8432
In Das U-Boot through 2020.01, a double free has been found in the cmd/gpt.c dorenamegptparts function. Double freeing may result in a write-what-where condition, allowing an attacker to execute arbitrary code. NOTE: this vulnerablity was introduced when attempting to fix a memory leak identified...