Snapdragon: Integer Overflow or Wraparound
CVE-2024-45555 is a high-severity integer overflow or wraparound vulnerability in Snapdragon from Qualcomm, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Snapdragon versions: MSM8996AU; QAM8255P; QAM8295P, 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.14% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Snapdragon you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on docs.qualcomm.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Qualcomm | Snapdragon | MSM8996AU; QAM8255P; QAM8295P; QAM8620P; QAM8650P; QAM8775P; QAMSRV1H; QAMSRV1M; and 32 more ranges | Not stated |
| Qualcomm | Msm8996au Firmware | Not specified in the record | Not stated |
| Qualcomm | Qam8255p Firmware | Not specified in the record | Not stated |
| Qualcomm | Qam8295p Firmware | Not specified in the record | Not stated |
| Qualcomm | Qam8620p Firmware | Not specified in the record | Not stated |
| Qualcomm | Qam8650p Firmware | Not specified in the record | Not stated |
| Qualcomm | Qam8775p Firmware | Not specified in the record | Not stated |
| Qualcomm | Qamsrv1h Firmware | Not specified in the record | Not stated |
| Qualcomm | Qamsrv1m 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 | Qca6574a Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6574au Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6584au Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6595 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6595au Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6688aq Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6696 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6698aq Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa6145p Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa6150p Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa6155 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa6155p Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa7255p Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa7775p Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE; 17 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- 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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.4 | High | CNA (qualcomm.com) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
Memory corruption can occur if an already verified IFS2 image is overwritten, bypassing boot verification. This allows unauthorized programs to be injected into security-sensitive images, enabling the booting of a tampered IFS2 system image.
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.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Snapdragon
- 7.1 High severity
- 7.0 High severity
Recent Integer Overflow or Wraparound vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
- 9.1 Critical severity
- 8.8 High severity
- 9.8 Critical severity
- 7.5 High severity
Spotted an error? Tell us.