Memory corruption via unchecked GP response length
Published Apr 16, 2020 · Updated Aug 4, 2024
Buffer overflow in GP command response handling in Qualcomm Snapdragon platforms allows remote attackers to corrupt memory via oversized responses. The handler writes a GP command response into its response buffer without first checking that the response length fits the destination. Network access and no authentication are required; Qualcomm has not disclosed whether the resulting memory corruption causes a crash, code execution, or another effect.
Summary
What happened
Buffer overflow in GP command response handling in Qualcomm Snapdragon platforms allows remote attackers to corrupt memory via oversized responses. The handler writes a GP command response into its response buffer without first checking that the response length fits the destination. Network access and no authentication are required; Qualcomm has not disclosed whether the resulting memory corruption causes a crash, code execution, or another effect.
The record
- CVE
- CVE-2019-10589
- Published
- Apr 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 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