Memory corruption via zero-byte buffer typecast
Published Apr 16, 2020 · Updated Aug 5, 2024
Out-of-bounds write in Qualcomm Snapdragon video firmware on QCS605, SA6155P, and SM8150 allows remote attackers to corrupt memory. The video component typecasts a zero-byte buffer as another structure and writes through it, overwriting memory beyond the allocation. Network reachability without authentication is sufficient, but public sources do not identify the video input or a bounded outcome beyond memory corruption.
Summary
What happened
Out-of-bounds write in Qualcomm Snapdragon video firmware on QCS605, SA6155P, and SM8150 allows remote attackers to corrupt memory. The video component typecasts a zero-byte buffer as another structure and writes through it, overwriting memory beyond the allocation. Network reachability without authentication is sufficient, but public sources do not identify the video input or a bounded outcome beyond memory corruption.
The record
- CVE
- CVE-2019-14132
- Published
- Apr 16, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 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