Physical memory corruption via boot argument length wraparound
Published Mar 17, 2021 · Updated Aug 4, 2024
Integer overflow in Qualcomm Snapdragon Consumer IOT, Industrial IOT, and Voice & Music allows physically proximate attackers to corrupt memory. The boot component accepts arguments without an adequate length check, allowing integer wraparound to make a subsequent buffer operation exceed its allocation. Physical access is required, but Qualcomm has not disclosed the affected routine, argument source, or precise post-corruption consequence.
Summary
What happened
Integer overflow in Qualcomm Snapdragon Consumer IOT, Industrial IOT, and Voice & Music allows physically proximate attackers to corrupt memory. The boot component accepts arguments without an adequate length check, allowing integer wraparound to make a subsequent buffer operation exceed its allocation. Physical access is required, but Qualcomm has not disclosed the affected routine, argument source, or precise post-corruption consequence.
The record
- CVE
- CVE-2020-11305
- Published
- Mar 17, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-680, CWE-119
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 17, 2021CVE 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