Arbitrary code execution via heap overflow
Published May 11, 2020 · Updated Aug 4, 2024
A heap overflow in Samsung Exynos devices on Android O, P, or Q allows attackers to execute code by bypassing Secure Bootloader protection. The vulnerable locus is the Secure Bootloader bootloader, which mishandles heap data and permits a buffer overflow that defeats secure-boot validation. The advisory does not specify attacker access prerequisites; successful exploitation compromises boot integrity and permits arbitrary code execution.
Summary
What happened
A heap overflow in Samsung Exynos devices on Android O, P, or Q allows attackers to execute code by bypassing Secure Bootloader protection. The vulnerable locus is the Secure Bootloader bootloader, which mishandles heap data and permits a buffer overflow that defeats secure-boot validation. The advisory does not specify attacker access prerequisites; successful exploitation compromises boot integrity and permits arbitrary code execution.
The record
- CVE
- CVE-2020-12746
- Published
- May 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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