Memory corruption via trusted-report buffer initialization
Published Apr 1, 2024 · Updated Aug 23, 2024
Buffer over-read in Qualcomm Snapdragon Trusted Execution Environment firmware allows local users to corrupt memory through trusted reports. During initialization for certain trusted-report types, the implementation reads beyond the intended buffer boundary; Qualcomm has not disclosed the responsible function or field. The flaw requires low-privileged local access and no user interaction, and its publicly disclosed consequence is memory corruption in the affected process.
Summary
What happened
Buffer over-read in Qualcomm Snapdragon Trusted Execution Environment firmware allows local users to corrupt memory through trusted reports. During initialization for certain trusted-report types, the implementation reads beyond the intended buffer boundary; Qualcomm has not disclosed the responsible function or field. The flaw requires low-privileged local access and no user interaction, and its publicly disclosed consequence is memory corruption in the affected process.
The record
- CVE
- CVE-2023-33115
- Published
- Apr 1, 2024
- Updated
- Aug 23, 2024
- Vendor
- Qualcomm
- Product
- Robotics RB3 Platform Firmware
- Classifications
- CWE-126
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 23, 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.
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