Local code execution via secure_log boundary failure
Published Dec 8, 2021 · Updated Aug 3, 2024
Out-of-bounds write in secure_log on selected Exynos Samsung Mobile Devices before SMR Dec-2021 Release 1 allows local users to execute code. The secure_log routines in BL31 and LDFW apply an improper boundary check, permitting a memory or register write beyond the intended range. Exploitation requires high local privileges and enables arbitrary memory modification and code execution in trusted firmware context.
Summary
What happened
Out-of-bounds write in secure_log on selected Exynos Samsung Mobile Devices before SMR Dec-2021 Release 1 allows local users to execute code. The secure_log routines in BL31 and LDFW apply an improper boundary check, permitting a memory or register write beyond the intended range. Exploitation requires high local privileges and enables arbitrary memory modification and code execution in trusted firmware context.
The record
- CVE
- CVE-2021-25518
- Published
- Dec 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-119, CWE-787, T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=P(9.0), Q(10.0), R(11.0) devices with selected Exynos chipsets <SMR Dec-2021 Release 1
What conditions does exploitation require?
What is affected?
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