CyberSecBulletin
CVE-2022-25658NVD status: Modified

Snapdragon Auto, Snapdragon Compute…: Improper Restriction of Operations within the Bounds of a Memory Buffer

Published Updated By the CyberSecBulletin desk

CVE-2022-25658 is a critical-severity improper restriction of operations within the bounds of a memory buffer 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 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.38% chance of exploitation within 30 days, which is low compared with other CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

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.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

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
QualcommCsra6620 FirmwareNot specified in the recordNot stated
QualcommCsra6640 FirmwareNot specified in the recordNot stated
QualcommMdm9206 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
QualcommMsm8953 FirmwareNot specified in the recordNot stated
QualcommMsm8996au FirmwareNot specified in the recordNot stated
QualcommQca4020 FirmwareNot specified in the recordNot stated
QualcommQca6174a FirmwareNot specified in the recordNot stated
QualcommQca6310 FirmwareNot specified in the recordNot stated
QualcommQca6320 FirmwareNot specified in the recordNot stated
QualcommQca6335 FirmwareNot specified in the recordNot stated
QualcommQca6390 FirmwareNot specified in the recordNot stated
QualcommQca6391 FirmwareNot specified in the recordNot stated
QualcommQca6420 FirmwareNot specified in the recordNot stated
QualcommQca6426 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
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 systemScoreSeverityScored by
CVSS 3.17.3HighCNA (qualcomm.com)
CVSS 3.19.8CriticalNVD

Official description

Memory corruption due to incorrect pointer arithmetic when attempting to change the endianness in video parser function 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: Improper Restriction of Operations within the Bounds of a Memory Buffer

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.

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 Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities (CWE-119)

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 Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities

Spotted an error? Tell us.