CVE-2020-8432: In Das U-Boot through 2020.01, a double free has been found in the cmd/gpt.c do_rename_gpt_parts() function.
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3% (FIRST EPSS); higher than 87.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: u-boot (Debian:12) 2020.01+dfsg-2; u-boot (openSUSE:Leap 15.1) 2019.01-lp151.6.13.1; u-boot (openSUSE:Leap 15.2) 2020.01-lp152.9.9.1.
Add it to your regular patch cycle. Upgrade to u-boot (Debian:12) 2020.01+dfsg-2; u-boot (openSUSE:Leap 15.1) 2019.01-lp151.6.13.1; u-boot (openSUSE:Leap 15.2) 2020.01-lp152.9.9.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 29, 2020
- Updated
- Jun 16, 2026
- EPSS
- 3.0% · 87th percentile
- CWE
- CWE-415
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- denx u-bootup to 2020.01 inclusive
- opensuse leap15.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | u-boot | before 2020.01+dfsg-2 | 2020.01+dfsg-2 |
| openSUSE:Leap 15.1 | u-boot | before 2019.01-lp151.6.13.1 | 2019.01-lp151.6.13.1 |
| openSUSE:Leap 15.2 | u-boot | before 2020.01-lp152.9.9.1 | 2020.01-lp152.9.9.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | u-boot | before 2018.03-4.6.1 | 2018.03-4.6.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | u-boot-rpi3 | before 2018.03-4.6.2 | 2018.03-4.6.2 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP1 | u-boot | before 2019.01-7.10.1 | 2019.01-7.10.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP1 | u-boot-rpi3 | before 2019.01-7.10.2 | 2019.01-7.10.2 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP2 | u-boot | before 2020.01-10.9.1 | 2020.01-10.9.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP2 | u-boot-rpiarm64 | before 2020.01-10.9.1 | 2020.01-10.9.1 |
| SUSE:Linux Enterprise Server 12 SP4-LTSS | u-boot | before 2018.03-4.3.1 | 2018.03-4.3.1 |
| SUSE:Linux Enterprise Server 12 SP4-LTSS | u-boot-rpi3 | before 2018.03-4.3.1 | 2018.03-4.3.1 |
| SUSE:Linux Enterprise Server 12 SP5 | u-boot | before 2019.01-5.3.1 | 2019.01-5.3.1 |
| SUSE:Linux Enterprise Server 12 SP5 | u-boot-rpi3 | before 2019.01-5.3.1 | 2019.01-5.3.1 |
Same product
denx: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-34835In Das U-Boot through 2022.07-rc5, an integer signedness error and resultant stack-based buffer overflow in the "i2c md" command enables the40Plan
- CVE-2022-30767nfs_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, le40Plan
- CVE-2019-14204An issue was discovered in Das U-Boot through 2019.07.40Plan
Published before and after this one in the same product
- ← EarlierCVE-2019-13105Aug 6, 2019 · Das U-Boot versions 2019.07-rc1 through 2019.07-rc4 can double-free a cached block of data when listing files in a crafted ext4 filesystem.31Monitor
- ← EarlierCVE-2019-13106Aug 6, 2019 · Das U-Boot versions 2016.09 through 2019.07-rc4 can memset() too much data while reading a crafted ext4 filesystem, which results in a stack32Monitor
- Later →CVE-2020-10648Mar 19, 2020 · Das U-Boot through 2020.01 allows attackers to bypass verified boot restrictions and subsequently boot arbitrary images by providing a craft31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:u-boot | 2020.01+dfsg-2 · Debian:12 | Package registry (OSV) |
| opensuse:u-boot | 2020.01-lp152.9.9.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| suse:u-boot | 2020.01-10.9.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP2 | Package registry (OSV) |
| suse:u-boot-rpi3 | 2019.01-5.3.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:u-boot-rpiarm64 | 2020.01-10.9.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-415 · Double FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.