CVE-2020-8432 json
In Das U-Boot through 2020.01, a double free has been found in the cmd/gpt.c do_rename_gpt_parts() function.
published 6y ago modified 4mo ago also EUVD-2020-29299
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
In Das U-Boot through 2020.01, a double free has been found in the cmd/gpt.c do_rename_gpt_parts() 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 by static analysis.
Patch / fix
- u-boot Debian 14, Debian 13, Debian 12 2020.01+dfsg-2
debian advisories DEBIAN-CVE-2020-8432
- u-boot Ubuntu 18.04 LTS 2020.10+dfsg-1ubuntu0~18.04.2
- u-boot Ubuntu 20.04 LTS 2021.01+dfsg-3ubuntu0~20.04.3
ubuntu advisories UBUNTU-CVE-2020-8432
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- u-boot SLES for SAP 15, SLES 15-LTSS, SLE High Performance Computing 15-LTSS +1 more 2018.03-4.6.1
- u-boot-rpi3 SLES 15-LTSS, SLE High Performance Computing 15-LTSS, SLE High Performance Computing 15-ESPOS 2018.03-4.6.2
- u-boot SLE Module for Basesystem 15 SP1 2019.01-7.10.1
- u-boot-rpi3 SLE Module for Basesystem 15 SP1 2019.01-7.10.2
- u-boot SLES for SAP 12 SP5, SLES 12 SP5 2019.01-5.3.1
- u-boot-rpi3 SLES for SAP 12 SP5, SLES 12 SP5 2019.01-5.3.1
- u-boot SLE Module for Basesystem 15 SP2 2020.01-10.9.1
- u-boot-rpiarm64 SLE Module for Basesystem 15 SP2 2020.01-10.9.1
suse advisories SUSE-SU-2020:3283-1SUSE-SU-2020:3282-1SUSE-SU-2020:3256-1SUSE-SU-2020:3255-1SUSE-SU-2020:3161-1
- u-boot openSUSE Leap 15.1 2019.01-lp151.6.13.1
- u-boot openSUSE Leap 15.2 2020.01-lp152.9.9.1
opensuse advisories openSUSE-SU-2020:1930-1openSUSE-SU-2020:1869-1
Is CVE-2020-8432 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-8432 updated cvss 8.1
uboot-tools: double free in do_rename_gpt_parts function in cmd/gpt.c
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.07% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
References
-
lists.opensuse.org
/opensuse-security-announce/2020-11/msg00030.html
vendor-advisory, mailing-list, third-party-advisory
- mail-archive.com /u-boot%40lists.denx.de/msg354060.html
- mail-archive.com /u-boot%40lists.denx.de/msg354114.html
Sources
- CVE List CVE-2020-8432
- NVD CVE-2020-8432
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.