Physical privilege escalation via insecure default value
Published Apr 13, 2021 · Updated Aug 3, 2024
Privilege management in MediaTek Little Kernel for Android SoC allows physically proximate attackers to gain elevated privileges. The public record identifies an insecure default value in the LK component but does not disclose the setting, code locus, or privileged operation it controls. Exploitation requires physical device access and user interaction, but no prior execution privileges, and can compromise confidentiality, integrity, and availability.
Summary
What happened
Privilege management in MediaTek Little Kernel for Android SoC allows physically proximate attackers to gain elevated privileges. The public record identifies an insecure default value in the LK component but does not disclose the setting, code locus, or privileged operation it controls. Exploitation requires physical device access and user interaction, but no prior execution privileges, and can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2021-0468
- Published
- Apr 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- MediaTek
- Product
- Little Kernel
- Classifications
- CWE-269, T1404
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 13, 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=Android SoC
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