Snapdragon Auto, Snapdragon Compute…: Buffer Copy without Checking Size of Input
CVE-2022-25686 is a critical-severity buffer copy without checking size of input vulnerability in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, 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. There is no confirmed exploitation so far. EPSS estimates a 0.45% 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 Industrial IOT, Snapdragon Mobile, 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 Industrial IOT, Snapdragon Mobile, Snapdragon Wearables | Not specified in the record | Not stated |
| Qualcomm | Apq8017 Firmware | Not specified in the record | Not stated |
| Qualcomm | Apq8053 Firmware | Not specified in the record | Not stated |
| Qualcomm | Aqt1000 Firmware | Not specified in the record | Not stated |
| Qualcomm | Msm8917 Firmware | Not specified in the record | Not stated |
| Qualcomm | Msm8953 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6390 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6391 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6420 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6426 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6430 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6436 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6574 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6574a Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6574au Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6595au Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6696 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcm2290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcm4290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcm6490 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcs2290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcs4290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcs6490 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qualcomm215 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa6155 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 | 7.3 | High | CNA (qualcomm.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
Memory corruption in video module due to buffer overflow while processing WAV file in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Buffer Copy without Checking Size of Input
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
More Buffer Copy without Checking Size of Input vulnerabilities (CWE-120)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
- 7.0 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Recent Buffer Copy without Checking Size of Input vulnerabilities
- 9.1 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.