Unspecified impact via uninitialized RILD variable
Published Apr 17, 2020 · Updated Aug 5, 2024
Uninitialized-variable use in RILD on LG Android 8.0 and 8.1 devices allows physically proximate attackers to cause unspecified impact. The radio-interface-layer daemon consumes a variable before it receives a defined value, making subsequent behavior depend on indeterminate state. Exposure is limited to DTAG-carrier software, while public records do not identify the trigger or resulting device behavior.
Summary
What happened
Uninitialized-variable use in RILD on LG Android 8.0 and 8.1 devices allows physically proximate attackers to cause unspecified impact. The radio-interface-layer daemon consumes a variable before it receives a defined value, making subsequent behavior depend on indeterminate state. Exposure is limited to DTAG-carrier software, while public records do not identify the trigger or resulting device behavior.
The record
- CVE
- CVE-2019-20785
- Published
- Apr 17, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-908
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
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