Local information disclosure via AVCS buffer over-read
Published Feb 6, 2024 · Updated Aug 6, 2024
Buffer over-read in Qualcomm Snapdragon Audio firmware allows local users to disclose data through an ADSP payload sent to AVCS services. Qualcomm identifies the locus only as Audio access to AVCS services from an ADSP payload and does not disclose the specific function or missing bounds check. A low-privilege local context is required; successful exploitation exposes protected data and can also interrupt the affected service.
Summary
What happened
Buffer over-read in Qualcomm Snapdragon Audio firmware allows local users to disclose data through an ADSP payload sent to AVCS services. Qualcomm identifies the locus only as Audio access to AVCS services from an ADSP payload and does not disclose the specific function or missing bounds check. A low-privilege local context is required; successful exploitation exposes protected data and can also interrupt the affected service.
The record
- CVE
- CVE-2023-33065
- Published
- Feb 6, 2024
- Updated
- Aug 6, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-125, CWE-126, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 6, 2024CVE publishedPublication date reported by the CVE source.
- Aug 6, 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