Memory corruption via SIM phonebook update request
Published Nov 4, 2024 · Updated Nov 16, 2024
Improper input validation in Qualcomm Snapdragon firmware allows local users to corrupt memory through an update SIM PB records request. The RIL request handler processes a SIM phonebook update without sufficient input validation, but Qualcomm has not disclosed the rejected field or corrupting memory operation. Exploitation requires high local privileges and no user interaction; successful corruption can compromise firmware confidentiality, integrity, and availability.
Summary
What happened
Improper input validation in Qualcomm Snapdragon firmware allows local users to corrupt memory through an update SIM PB records request. The RIL request handler processes a SIM phonebook update without sufficient input validation, but Qualcomm has not disclosed the rejected field or corrupting memory operation. Exploitation requires high local privileges and no user interaction; successful corruption can compromise firmware confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-33031
- Published
- Nov 4, 2024
- Updated
- Nov 16, 2024
- Vendor
- Qualcomm
- Product
- Qualcomm WCN3660B Firmware
- Classifications
- CWE-20
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 4, 2024CVE publishedPublication date reported by the CVE source.
- Nov 16, 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