Memory corruption via unchecked clip offset
Published Jan 21, 2020 · Updated Aug 5, 2024
Buffer overflow in Qualcomm Snapdragon video processing allows remote attackers to corrupt memory through a nonstandard media clip. The closed-source parser plays the clip without checking an offset against the available length, allowing an out-of-bounds write. No privileges or user interaction are required, but public records do not identify the affected codec, entry point, or whether corruption yields code execution or only a crash.
Summary
What happened
Buffer overflow in Qualcomm Snapdragon video processing allows remote attackers to corrupt memory through a nonstandard media clip. The closed-source parser plays the clip without checking an offset against the available length, allowing an out-of-bounds write. No privileges or user interaction are required, but public records do not identify the affected codec, entry point, or whether corruption yields code execution or only a crash.
The record
- CVE
- CVE-2019-14006
- Published
- Jan 21, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 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