Memory corruption via unvalidated application array length
Published Jun 22, 2020 · Updated Aug 4, 2024
Memory corruption in Qualcomm Snapdragon perfservice allows local users to corrupt process memory through an application-supplied array length. Perfservice accepts the array length without adequately validating it before memory access, enabling an out-of-bounds write. A local application with low privileges and no user interaction can trigger the flaw; public evidence does not specify whether the result is a crash, code execution, or another consequence.
Summary
What happened
Memory corruption in Qualcomm Snapdragon perfservice allows local users to corrupt process memory through an application-supplied array length. Perfservice accepts the array length without adequately validating it before memory access, enabling an out-of-bounds write. A local application with low privileges and no user interaction can trigger the flaw; public evidence does not specify whether the result is a crash, code execution, or another consequence.
The record
- CVE
- CVE-2020-3676
- Published
- Jun 22, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 22, 2020CVE 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