Snapdragon Auto, Snapdragon Consumer IOT…: Integer Overflow or Wraparound
CVE-2022-22105 is a critical-severity integer overflow or wraparound vulnerability in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music 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.52% 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 Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music 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 Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music | Not specified in the record | Not stated |
| Qualcomm | Apq8009 Firmware | 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 | Apq8096au Firmware | Not specified in the record | Not stated |
| Qualcomm | Ar8031 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 | Mdm9150 Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm9250 Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm9607 Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm9626 Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm9628 Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm9640 Firmware | Not specified in the record | Not stated |
| Qualcomm | Mdm9650 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca4020 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6174a Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6564a Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6564au 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 | Qca6584 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6595 Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE; 27 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.4 | Critical | CNA (qualcomm.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
Memory corruption in bluetooth due to integer overflow while processing HFP-UNIT profile in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Integer Overflow or Wraparound
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
How developers prevent this class of flaw
- Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).
More Integer Overflow or Wraparound vulnerabilities (CWE-190)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Recent Integer Overflow or Wraparound vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.