Hypervisor code execution via unchecked physical addresses
Published Apr 7, 2020 · Updated Aug 5, 2024
Memory corruption in Samsung RKP on Android 6.0 and 7.0 allows local users with kernel code execution to gain hypervisor control. The cfp_ropp_new_key and cfp_ropp_new_key_reenc handlers convert attacker-supplied kernel virtual addresses to physical addresses without rejecting RKP or stage-2-protected ranges, then write an XOR-derived 64-bit value there. Reachability requires prior EL1 kernel code execution and an affected Exynos 7420, Exynos 8890, or MSM8996 device; successful corruption permits EL2 code modification.
Summary
What happened
Memory corruption in Samsung RKP on Android 6.0 and 7.0 allows local users with kernel code execution to gain hypervisor control. The cfp_ropp_new_key and cfp_ropp_new_key_reenc handlers convert attacker-supplied kernel virtual addresses to physical addresses without rejecting RKP or stage-2-protected ranges, then write an XOR-derived 64-bit value there. Reachability requires prior EL1 kernel code execution and an affected Exynos 7420, Exynos 8890, or MSM8996 device; successful corruption permits EL2 code modification.
The record
- CVE
- CVE-2017-18696
- Published
- Apr 7, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 7, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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