Local telecom-service crash via missing permission check
Published Apr 11, 2023 · Updated Feb 10, 2025
NULL pointer dereference in UNISOC telecom service on affected Android 10 and Android 11 chipsets allows local users to crash the service. UNISOC identifies the locus only as telecom service and states that it omits a permission check; no function, request type, or pointer operation is public. Low-privileged local access is required, and the published impact is limited to loss of telecom-service availability.
Summary
What happened
NULL pointer dereference in UNISOC telecom service on affected Android 10 and Android 11 chipsets allows local users to crash the service. UNISOC identifies the locus only as telecom service and states that it omits a permission check; no function, request type, or pointer operation is public. Low-privileged local access is required, and the published impact is limited to loss of telecom-service availability.
The record
- CVE
- CVE-2022-47468
- Published
- Apr 11, 2023
- Updated
- Feb 10, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 11, 2023CVE publishedPublication date reported by the CVE source.
- Feb 10, 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?
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