Local privilege escalation via arbitrary read
Published Jan 21, 2021 · Updated Aug 4, 2024
An arbitrary-read flaw in Qualcomm admin services in an unspecified Windows environment allows local users to gain privileged read access. The published record identifies an arbitrary read but does not disclose the affected service, input, or operation that enables the read. A low-privileged local account is required, and the documented consequence is limited to reading confidential data across a privilege boundary.
Summary
What happened
An arbitrary-read flaw in Qualcomm admin services in an unspecified Windows environment allows local users to gain privileged read access. The published record identifies an arbitrary read but does not disclose the affected service, input, or operation that enables the read. A low-privileged local account is required, and the documented consequence is limited to reading confidential data across a privilege boundary.
The record
- CVE
- CVE-2020-3687
- Published
- Jan 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 21, 2021CVE 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.
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