Unauthenticated remote code execution
Published Nov 29, 2023 · Updated Jun 5, 2025
Remote code execution in the AMLogic Secure Monitor in Google Android SoC allows remote attackers to execute code via unspecified vectors. Google identifies the Secure Monitor subcomponent but has not published the input path or unsafe operation that enables execution. Network access requires no authentication or user interaction, and successful exploitation grants code execution on the device.
Summary
What happened
Remote code execution in the AMLogic Secure Monitor in Google Android SoC allows remote attackers to execute code via unspecified vectors. Google identifies the Secure Monitor subcomponent but has not published the input path or unsafe operation that enables execution. Network access requires no authentication or user interaction, and successful exploitation grants code execution on the device.
The record
- CVE
- CVE-2022-42541
- Published
- Nov 29, 2023
- Updated
- Jun 5, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-94
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 29, 2023CVE publishedPublication date reported by the CVE source.
- Jun 5, 2025Record 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?
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