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-2024-49829: CWE-120 Buffer Copy Without Checking Size of Input ('Classic Buffer Overflow') in Qualcomm, Inc. Snapdragon

0
Medium
VulnerabilityCVE-2024-49829cvecve-2024-49829cwe-120
Published: Tue May 06 2025 (05/06/2025, 08:32:14 UTC)
Source: CVE
Vendor/Project: Qualcomm, Inc.
Product: Snapdragon

Description

Memory corruption can occur during context user dumps due to inadequate checks on buffer length.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 20:25:02 UTC

Technical Analysis

CVE-2024-49829 is a classic buffer overflow vulnerability (CWE-120) identified in Qualcomm Snapdragon chipsets, specifically during the process of context user dumps. The root cause is inadequate validation of buffer length before copying data, which leads to memory corruption. This vulnerability affects a range of Qualcomm products including FastConnect 6900 and 7800 subsystems, Snapdragon 429 Mobile Platform, Snapdragon 8 Gen 1 Mobile Platform, and several wireless connectivity modules such as WCD9380 and WCN3620. The flaw allows an attacker with high-level privileges on the device to trigger a buffer overflow, potentially leading to arbitrary code execution, privilege escalation, or system crashes. The CVSS v3.1 base score is 6.7, reflecting a medium severity with high impact on confidentiality, integrity, and availability, but requiring local privileged access and no user interaction. No public exploits or active exploitation in the wild have been reported as of now. The vulnerability is particularly critical because Snapdragon chipsets are widely used in mobile phones, IoT devices, and embedded systems, making the attack surface broad. The lack of current patches increases the urgency for affected parties to monitor vendor advisories and prepare for remediation. The vulnerability highlights the importance of rigorous input validation in low-level firmware and driver components to prevent memory corruption issues.

Potential Impact

The vulnerability can lead to significant security impacts including unauthorized disclosure of sensitive information (confidentiality), unauthorized modification or corruption of system data (integrity), and denial of service or system instability (availability). Since exploitation requires local privileged access, the immediate risk is limited to attackers who have already compromised lower privilege levels or insiders with elevated rights. However, successful exploitation could enable attackers to escalate privileges, execute arbitrary code, or disrupt device functionality. Given the widespread deployment of Snapdragon chipsets in smartphones, tablets, IoT devices, and embedded systems globally, the potential impact extends to millions of devices. This can affect consumer privacy, enterprise mobile security, and critical infrastructure relying on embedded Qualcomm hardware. The absence of known exploits reduces immediate threat but does not eliminate the risk of future attacks once exploit code becomes available. Organizations relying on affected hardware must consider the vulnerability in their risk assessments and incident response planning.

Mitigation Recommendations

1. Apply security patches and firmware updates from Qualcomm or device manufacturers as soon as they are released. 2. Restrict and monitor privileged access on devices using affected Snapdragon platforms to minimize the risk of local exploitation. 3. Implement strict access controls and endpoint security measures to prevent unauthorized local access. 4. Employ runtime protections such as memory protection mechanisms (e.g., DEP, ASLR) where supported by the device to mitigate exploitation impact. 5. Monitor system logs and behavior for signs of memory corruption or unexpected crashes that could indicate exploitation attempts. 6. For organizations deploying IoT or embedded devices with affected chipsets, ensure secure device provisioning and update mechanisms are in place. 7. Engage with vendors to obtain timely vulnerability disclosures and coordinate patch management. 8. Consider network segmentation and limiting device exposure to reduce attack surface. 9. Conduct regular security assessments and penetration testing focusing on local privilege escalation vectors. 10. Educate users and administrators about the importance of applying updates and maintaining device security hygiene.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
qualcomm
Date Reserved
2024-10-20T17:18:43.214Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d981bc4522896dcbd9c96

Added to database: 5/21/2025, 9:08:43 AM

Last enriched: 2/26/2026, 8:25:02 PM

Last updated: 3/25/2026, 5:05:26 AM

Views: 56

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses