Snapdragon Auto, Snapdragon Compute…: Improper Validation of Array Index
CVE-2022-25720 is a critical-severity improper validation of array index vulnerability in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables from Qualcomm, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables versions: APQ8009; APQ8009W; APQ8017, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.51% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on qualcomm.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Qualcomm | Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables | APQ8009; APQ8009W; APQ8017; APQ8052; APQ8053; APQ8056; APQ8064AU; APQ8076; and 32 more ranges | Not stated |
| Qualcomm | Apq8009 Firmware | Not specified in the record | Not stated |
| Qualcomm | Apq8009w Firmware | Not specified in the record | Not stated |
| Qualcomm | Apq8017 Firmware | Not specified in the record | Not stated |
| Qualcomm | Apq8052 Firmware | Not specified in the record | Not stated |
| Qualcomm | Apq8053 Firmware | Not specified in the record | Not stated |
| Qualcomm | Apq8056 Firmware | Not specified in the record | Not stated |
| Qualcomm | Apq8064au Firmware | Not specified in the record | Not stated |
| Qualcomm | Apq8076 Firmware | Not specified in the record | Not stated |
| Qualcomm | Apq8096au Firmware | Not specified in the record | Not stated |
| Qualcomm | Aqt1000 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ar6003 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ar8031 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ar8035 Firmware | Not specified in the record | Not stated |
| Qualcomm | Csra6620 Firmware | Not specified in the record | Not stated |
| Qualcomm | Csra6640 Firmware | Not specified in the record | Not stated |
| Qualcomm | Csrb31024 Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm8215 Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm8215m Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm8615m Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm9150 Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm9206 Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm9215 Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm9230 Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm9250 Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | CNA (qualcomm.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
Memory corruption in WLAN due to out of bound array access during connect/roaming in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Validation of Array Index
The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.
How developers prevent this class of flaw
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, Ada allows the programmer to constrain the values of a variable and languages such as Java and Ruby will allow the programmer to handle exceptions when an out-of-bounds index is accessed.
- Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment. For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND.
More Improper Validation of Array Index vulnerabilities (CWE-129)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
Recent Improper Validation of Array Index vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
- 8.8 High severity
Spotted an error? Tell us.