Local memory corruption via invalid backend ID
Published Sep 2, 2022 · Updated Aug 3, 2024
Out-of-bounds write in Snapdragon PCM routing process in Qualcomm Snapdragon chipsets allows local users to cause memory corruption via crafted backend IDs. The routing process fails to validate a backend identifier before using it, enabling an out-of-range pointer operation that corrupts memory. Exploitation requires local access to a device running affected Snapdragon firmware; the resulting corruption can affect confidentiality, integrity, and availability, but no remote network path is described.
Summary
What happened
Out-of-bounds write in Snapdragon PCM routing process in Qualcomm Snapdragon chipsets allows local users to cause memory corruption via crafted backend IDs. The routing process fails to validate a backend identifier before using it, enabling an out-of-range pointer operation that corrupts memory. Exploitation requires local access to a device running affected Snapdragon firmware; the resulting corruption can affect confidentiality, integrity, and availability, but no remote network path is described.
The record
- CVE
- CVE-2022-22080
- Published
- Sep 2, 2022
- Updated
- Aug 3, 2024
- Vendor
- Qualcomm
- Product
- Snapdragon
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=APQ8053, APQ8096AU, AQT1000, AR8031, AR8035, CSRA6620, CSRA6640, MDM9150, MDM9628, MDM9640, MDM9650, MSM8953, QCA6174A, QCA6390, QCA6391, QCA6420, QCA6426, QCA6430, QCA6436, QCA6564, QCA6564A, QCA6564AU, QCA6574, QCA6574A, QCA6574AU, QCA6595AU, QCA6696, QCA8337, QCA9377, QCM2290, QCM4290, QCM6490, QCS2290, QCS405, QCS410, QCS4290, QCS610, QCS6490, QRB5165, QRB5165M, QRB5165N, SA415M, SA515M, SA6145P, SA6155, SA6155P, SA8155, SA8155P, SA8195P, SD 675, SD439, SD460, SD480, SD660, SD662, SD675, SD678, SD680, SD690 5G, SD695, SD720G, SD730, SD750G, SD765, SD765G, SD768G, SD778G, SD780G, SD855, SD865 5G, SD870, SD888, SD888 5G, SDX12, SDX50M, SDX55, SDX55M, SDXR2 5G, SM4125, SM6250, SM6250P, SM7250P, SM7315, SM7325P, WCD9326, WCD9335, WCD9341, WCD9360, WCD9370, WCD9371, WCD9375, WCD9380, WCD9385, WCN3615, WCN3680B, WCN3910, WCN3950, WCN3980, WCN3988, WCN3990, WCN3991, WCN3998, WCN3999, WCN6740, WCN6750, WCN6850, WCN6851, WCN6855, WCN6856, WCN7850, WCN7851, WSA8810, WSA8815, WSA8830, WSA8835
What conditions does exploitation require?
What is affected?
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