Arbitrary code execution via GPT rename double free
Published Jan 29, 2020 · Updated Aug 4, 2024
A double-free vulnerability in Das U-Boot through 2020.01 allows remote attackers to execute arbitrary code via crafted GPT partition rename input. The cmd/gpt.c do_rename_gpt_parts() function frees the same allocation twice while processing partition-name data, enabling a write-what-where condition. Exploitation requires access to the U-Boot GPT rename command; successful corruption can overwrite attacker-chosen memory and transfer execution.
Summary
What happened
A double-free vulnerability in Das U-Boot through 2020.01 allows remote attackers to execute arbitrary code via crafted GPT partition rename input. The cmd/gpt.c do_rename_gpt_parts() function frees the same allocation twice while processing partition-name data, enabling a write-what-where condition. Exploitation requires access to the U-Boot GPT rename command; successful corruption can overwrite attacker-chosen memory and transfer execution.
The record
- CVE
- CVE-2020-8432
- Published
- Jan 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo