CyberSecBulletin
CVE-2022-22074NVD status: Modified

Snapdragon Auto, Snapdragon Compute…: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2022-22074 is a high-severity integer overflow or wraparound vulnerability in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables 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. There is no confirmed exploitation so far. EPSS estimates a 0.12% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of Snapdragon Auto, Snapdragon Compute, Snapdragon 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.
  2. Read the advisory on qualcomm.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
QualcommSnapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon WearablesNot specified in the recordNot stated
QualcommApq8009 FirmwareNot specified in the recordNot stated
QualcommApq8009w FirmwareNot specified in the recordNot stated
QualcommApq8017 FirmwareNot specified in the recordNot stated
QualcommApq8053 FirmwareNot specified in the recordNot stated
QualcommApq8096au FirmwareNot specified in the recordNot stated
QualcommAqt1000 FirmwareNot specified in the recordNot stated
QualcommAr8031 FirmwareNot specified in the recordNot stated
QualcommAr8035 FirmwareNot specified in the recordNot stated
QualcommCsra6620 FirmwareNot specified in the recordNot stated
QualcommCsra6640 FirmwareNot specified in the recordNot stated
QualcommCsrb31024 FirmwareNot specified in the recordNot stated
QualcommMdm9150 FirmwareNot specified in the recordNot stated
QualcommMdm9206 FirmwareNot specified in the recordNot stated
QualcommMdm9250 FirmwareNot specified in the recordNot stated
QualcommMdm9607 FirmwareNot specified in the recordNot stated
QualcommMdm9626 FirmwareNot specified in the recordNot stated
QualcommMdm9628 FirmwareNot specified in the recordNot stated
QualcommMdm9640 FirmwareNot specified in the recordNot stated
QualcommMdm9650 FirmwareNot specified in the recordNot stated
QualcommMsm8909w FirmwareNot specified in the recordNot stated
QualcommMsm8917 FirmwareNot specified in the recordNot stated
QualcommMsm8937 FirmwareNot specified in the recordNot stated
QualcommMsm8953 FirmwareNot specified in the recordNot stated
QualcommMsm8996au FirmwareNot specified in the recordNot 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
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 systemScoreSeverityScored by
CVSS 3.18.4HighCNA (qualcomm.com)
CVSS 3.17.8HighNVD

Official description

Memory Corruption during wma file playback due to integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon 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: 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

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

All Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables vulnerabilities

Recent Integer Overflow or Wraparound vulnerabilities

Spotted an error? Tell us.