Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2023-33055: CWE-120 Buffer Copy Without Checking Size of Input ('Classic Buffer Overflow') in Qualcomm, Inc. Snapdragon

0
High
VulnerabilityCVE-2023-33055cvecve-2023-33055cwe-120
Published: Tue Nov 07 2023 (11/07/2023, 05:26:50 UTC)
Source: CVE Database V5
Vendor/Project: Qualcomm, Inc.
Product: Snapdragon

Description

CVE-2023-33055 is a high-severity buffer overflow vulnerability in Qualcomm Snapdragon platforms affecting a wide range of mobile, wearable, automotive, and IoT devices. The flaw arises from improper size checking during a buffer copy operation in the audio driver callback function within the ADSP (Audio DSP) subsystem, leading to memory corruption. Exploitation requires local privileges and no user interaction but can result in full confidentiality, integrity, and availability compromise. This vulnerability impacts numerous Snapdragon chipsets widely used in smartphones and embedded devices across Europe. Although no known exploits are currently reported in the wild, the potential for privilege escalation or arbitrary code execution is significant. European organizations relying on affected devices should prioritize patching once available and implement strict access controls to mitigate risk. Countries with high smartphone penetration and strong industrial IoT adoption are most at risk. The vulnerability is rated with a CVSS score of 7. 8 (high), reflecting its serious impact and moderate exploit complexity.

AI-Powered Analysis

AILast updated: 12/23/2025, 18:26:17 UTC

Technical Analysis

CVE-2023-33055 is a classic buffer overflow vulnerability (CWE-120) identified in the Qualcomm Snapdragon platform's audio driver, specifically within the ADSP (Audio Digital Signal Processor) subsystem. The issue stems from a buffer copy operation that does not properly check the size of the input data before copying, leading to memory corruption. This flaw can be triggered when invoking a callback function in the audio driver, potentially allowing an attacker with local privileges to corrupt memory, leading to arbitrary code execution, privilege escalation, or denial of service. The vulnerability affects a broad range of Qualcomm products, including many Snapdragon mobile platforms (from Snapdragon 4 Gen 1 to Snapdragon 8+ Gen 2), FastConnect wireless subsystems, automotive platforms, wearable platforms, and various modem-RF systems. The vulnerability requires local access with low privileges but does not require user interaction, making it a potent vector for attackers who have gained limited access to the device. The CVSS v3.1 score of 7.8 reflects high confidentiality, integrity, and availability impacts, with low attack complexity and limited privileges required. No public exploits are currently known, but the extensive list of affected platforms indicates a widespread risk across multiple device categories. The vulnerability was published on November 7, 2023, and remains unpatched as per the provided data, emphasizing the urgency for mitigation.

Potential Impact

For European organizations, the impact of CVE-2023-33055 is significant due to the widespread use of Qualcomm Snapdragon chipsets in smartphones, tablets, automotive systems, and IoT devices. Successful exploitation could allow attackers to escalate privileges locally, execute arbitrary code, or cause denial of service, potentially compromising sensitive corporate data, disrupting communications, or affecting critical infrastructure relying on embedded Qualcomm platforms. In sectors such as finance, healthcare, manufacturing, and automotive, where Snapdragon-based devices are prevalent, this vulnerability could lead to data breaches, operational disruptions, or safety risks. The high confidentiality impact means sensitive information stored or processed on affected devices could be exposed. Integrity and availability impacts raise concerns about device reliability and trustworthiness, which are critical for industrial control systems and connected vehicles. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially given the vulnerability's high severity and broad device coverage. European organizations with Bring Your Own Device (BYOD) policies or those deploying Snapdragon-based IoT devices should be particularly vigilant.

Mitigation Recommendations

1. Monitor Qualcomm and device vendors for official patches and apply them promptly once released. 2. Implement strict access controls on devices using affected Snapdragon platforms to limit local privilege escalation opportunities. 3. Employ mobile device management (MDM) solutions to enforce security policies, restrict installation of untrusted applications, and monitor device behavior. 4. For embedded and IoT devices, isolate vulnerable devices on segmented networks to reduce attack surface and lateral movement potential. 5. Conduct regular security audits and vulnerability assessments on devices incorporating affected Qualcomm chipsets. 6. Educate users and administrators about the risks of local privilege escalation vulnerabilities and the importance of applying updates. 7. Where possible, disable or restrict audio driver callback functionalities if not essential, as a temporary mitigation. 8. Utilize endpoint detection and response (EDR) tools capable of identifying anomalous behavior indicative of exploitation attempts. 9. Collaborate with suppliers and vendors to ensure timely vulnerability management and patch deployment in supply chains.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
qualcomm
Date Reserved
2023-05-17T09:28:53.125Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 694194789050fe8508060cbd

Added to database: 12/16/2025, 5:18:48 PM

Last enriched: 12/23/2025, 6:26:17 PM

Last updated: 2/6/2026, 8:59:52 AM

Views: 25

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats