Memory corruption via key-blob buffer over-read
Published Jul 1, 2024 · Updated Aug 1, 2024
Buffer over-read in Qualcomm Snapdragon firmware's trusted execution environment allows local users to corrupt memory through a crafted key blob. The key-blob processing routine reads beyond the supplied buffer while decoding user-controlled key material. Low-privileged local access is required; successful exploitation compromises confidentiality, integrity, and availability.
Summary
What happened
Buffer over-read in Qualcomm Snapdragon firmware's trusted execution environment allows local users to corrupt memory through a crafted key blob. The key-blob processing routine reads beyond the supplied buffer while decoding user-controlled key material. Low-privileged local access is required; successful exploitation compromises confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-21465
- Published
- Jul 1, 2024
- Updated
- Aug 1, 2024
- Vendor
- Qualcomm
- Product
- Robotics RB3 Platform Firmware
- Classifications
- CWE-125, CWE-126
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=0 <=*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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