CyberSecBulletin
CVE-2023-33106Exploited in the wildNVD status: Analyzed

Qualcomm Multiple Chipsets Use of Out-of-Range Pointer Offset

Published Updated By the CyberSecBulletin desk

CVE-2023-33106 is a high-severity improper restriction of operations within the bounds of a memory buffer 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: AR8035; CSRA6620; CSRA6640, and others listed below. The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on December 5, 2023, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Check which version of Snapdragon you run against the affected versions below, and install the vendor's latest release.
  2. CISA's required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
  3. Read the advisory on qualcomm.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
QualcommSnapdragonAR8035; CSRA6620; CSRA6640; FastConnect 6200; FastConnect 6700; FastConnect 6800; FastConnect 6900; FastConnect 7800; and 32 more rangesNot stated
Qualcommar8035_firmwareall versionsNot stated
Qualcommcsra6620_firmwareall versionsNot stated
Qualcommcsra6640_firmwareall versionsNot stated
Qualcommfastconnect_6200_firmwareall versionsNot stated
Qualcommfastconnect_6700_firmwareall versionsNot stated
Qualcommfastconnect_6800_firmwareall versionsNot stated
Qualcommfastconnect_6900_firmwareall versionsNot stated
Qualcommfastconnect_7800_firmwareall versionsNot stated
Qualcommflight_rb5_5g_platform_firmwareall versionsNot stated
Qualcommqam8255p_firmwareall versionsNot stated
Qualcommqam8295p_firmwareall versionsNot stated
Qualcommqam8650p_firmwareall versionsNot stated
Qualcommqam8775p_firmwareall versionsNot stated
Qualcommqca6174a_firmwareall versionsNot stated
Qualcommqca6391_firmwareall versionsNot stated
Qualcommqca6426_firmwareall versionsNot stated
Qualcommqca6436_firmwareall versionsNot stated
Qualcommqca6574_firmwareall versionsNot stated
Qualcommqca6574a_firmwareall versionsNot stated
Qualcommqca6574au_firmwareall versionsNot stated
Qualcommqca6595_firmwareall versionsNot stated
Qualcommqca6595au_firmwareall versionsNot stated
Qualcommqca6696_firmwareall versionsNot stated
Qualcommqca6698aq_firmwareall versionsNot 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 while submitting a large list of sync points in an AUX command to the IOCTL_KGSL_GPU_AUX_COMMAND.

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. Added to CISA's Known Exploited Vulnerabilities catalogue.
  3. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  4. Deadline for US federal agencies to remediate, set by CISA.
  5. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in Snapdragon

All Snapdragon vulnerabilities

Recent Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities

Spotted an error? Tell us.