Unauthenticated remote code execution
Published Nov 29, 2023 · Updated Aug 3, 2024
Remote code execution in Google Android SoC's AMLogic Secure Monitor allows remote attackers to execute code via unspecified vectors. Google identifies the affected subcomponent but has not published the Secure Monitor operation that mishandles untrusted input. Exploitation requires network reachability, needs no authentication or user interaction, and grants code execution in the affected context.
Summary
What happened
Remote code execution in Google Android SoC's AMLogic Secure Monitor allows remote attackers to execute code via unspecified vectors. Google identifies the affected subcomponent but has not published the Secure Monitor operation that mishandles untrusted input. Exploitation requires network reachability, needs no authentication or user interaction, and grants code execution in the affected context.
The record
- CVE
- CVE-2022-42537
- Published
- Nov 29, 2023
- Updated
- Aug 3, 2024
- Vendor
- Product
- Android
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 29, 2023CVE 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
No sourced classifications are available.
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