Memory corruption via unterminated source byte array
Published Jan 21, 2020 · Updated Aug 5, 2024
Buffer overflow in Qualcomm Snapdragon video components allows remote attackers to corrupt memory through malformed byte-array input. A source is read as a byte array without a terminating null byte, causing incorrect input to overrun the destination buffer. Network delivery requires no authentication or user interaction, but the closed-source record discloses neither the accepted input format nor a demonstrated outcome beyond memory corruption.
Summary
What happened
Buffer overflow in Qualcomm Snapdragon video components allows remote attackers to corrupt memory through malformed byte-array input. A source is read as a byte array without a terminating null byte, causing incorrect input to overrun the destination buffer. Network delivery requires no authentication or user interaction, but the closed-source record discloses neither the accepted input format nor a demonstrated outcome beyond memory corruption.
The record
- CVE
- CVE-2019-14014
- Published
- Jan 21, 2020
- Updated
- Aug 5, 2024
- Vendor
- Qualcomm
- Product
- Snapdragon
- Classifications
- CWE-120
- 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Nicobar, SDM670, SDM710, SDM845, SM6150, SM8150, SM8250, SXR2130
What conditions does exploitation require?
What is affected?
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