Remote memory corruption via stale global audio pointer
Published Jan 21, 2020 · Updated Aug 4, 2024
Use-after-free in Qualcomm Snapdragon audio components allows remote attackers to access freed memory through a network-reachable audio path. The cleanup path frees an audio-device object but assigns NULL to a local pointer instead of the global static pointer, leaving the global pointer dangling. Network access and no authentication are required; Qualcomm does not identify the triggering audio operation or resulting execution context.
Summary
What happened
Use-after-free in Qualcomm Snapdragon audio components allows remote attackers to access freed memory through a network-reachable audio path. The cleanup path frees an audio-device object but assigns NULL to a local pointer instead of the global static pointer, leaving the global pointer dangling. Network access and no authentication are required; Qualcomm does not identify the triggering audio operation or resulting execution context.
The record
- CVE
- CVE-2019-10581
- Published
- Jan 21, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 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.
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