Physical code execution via EFI structure overwrite
Published Apr 3, 2020 · Updated Sep 17, 2024
Use-after-free in Dell Latitude 7202 Rugged Tablet BIOS before A28 allows physically proximate attackers to execute code in SMM. The affected SMM path uses EFI_BOOT_SERVICES after its lifetime ends, allowing the structure to be overwritten before subsequent use. Physical access is required; successful exploitation gains arbitrary code execution in SMM, beneath the operating system.
Summary
What happened
Use-after-free in Dell Latitude 7202 Rugged Tablet BIOS before A28 allows physically proximate attackers to execute code in SMM. The affected SMM path uses EFI_BOOT_SERVICES after its lifetime ends, allowing the structure to be overwritten before subsequent use. Physical access is required; successful exploitation gains arbitrary code execution in SMM, beneath the operating system.
The record
- CVE
- CVE-2020-5348
- Published
- Apr 3, 2020
- Updated
- Sep 17, 2024
- Vendor
- Dell
- Product
- Dell Client Platform BIOS
- Classifications
- CWE-416
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <A28
What conditions does exploitation require?
What is affected?
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