System crash via open_exec NULL pointer dereference
Published Jan 18, 2022 · Updated Aug 4, 2024
NULL pointer dereference in Allwinner R818 SoC Android Q SDK 1.0 allows remote attackers to crash the system via a malicious executable. The open_exec syscall handler dereferences a NULL pointer while processing the file for execution. No authentication or user interaction is required, and the documented consequence is a system crash without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in Allwinner R818 SoC Android Q SDK 1.0 allows remote attackers to crash the system via a malicious executable. The open_exec syscall handler dereferences a NULL pointer while processing the file for execution. No authentication or user interaction is required, and the documented consequence is a system crash without reported data disclosure or modification.
The record
- CVE
- CVE-2021-38784
- Published
- Jan 18, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1642
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 18, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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