VulnerabilityPublished 3 Jun 2025

CVE-2024-53019: Qualcomm Snapdragon · Buffer Over-read

Affects Qualcomm SnapdragonSource CVE Database V5

Not known to be exploited · CVSS 8.2 High.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Monitor Qualcomm and device manufacturers for official patches or firmware updates addressing CVE-2024-53019 and prioritize their deployment across all affected devices.
Implement network-level filtering to block or scrutinize RTP traffic from untrusted sources, especially on corporate Wi-Fi and VPN gateways, to reduce exposure to crafted malicious packets.
Employ intrusion detection/prevention systems (IDS/IPS) with updated signatures capable of detecting anomalous RTP packet structures indicative of exploitation attempts.
Enforce strict network segmentation and limit exposure of vulnerable devices to untrusted networks, including guest Wi-Fi and public internet.
For managed mobile devices, use Mobile Device Management (MDM) solutions to enforce security policies, control application permissions, and remotely update or quarantine vulnerable devices.
Educate users on the risks of connecting to unsecured networks and encourage the use of VPNs to protect RTP traffic confidentiality.
Conduct regular security audits and vulnerability assessments focusing on mobile endpoints and wireless infrastructure to identify and remediate potential attack vectors.
Where feasible, disable or restrict RTP-based services on devices that do not require them, minimizing the attack surface.

Description

Information disclosure may occur while decoding the RTP packet with improper header length for number of contributing sources.

Impact

For European organizations, the impact of CVE-2024-53019 is considerable due to the extensive use of Qualcomm Snapdragon chipsets in consumer and enterprise mobile devices, including smartphones, tablets, and IoT devices. Confidential information such as cryptographic keys, user credentials, or sensitive application data could be exposed through memory disclosure. This could facilitate further attacks such as identity theft, corporate espionage, or unauthorized access to corporate networks. The vulnerability's network-based exploitation vector means attackers can remotely target devices without requiring physical access or user interaction, increasing the risk in environments with exposed or poorly segmented networks. Enterprises relying on mobile devices for secure communications, remote work, or sensitive data processing may face data breaches or compliance violations under GDPR if personal data is leaked. Additionally, the vulnerability could undermine trust in mobile communications and impact sectors such as finance, healthcare, and government agencies that rely heavily on secure mobile platforms. The lack of current exploits provides a window for mitigation, but the broad range of affected devices means many endpoints remain at risk until patches are available and deployed.

CWE-126Buffer Over-read (opens in a new tab)
Variant weakness
The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

docs.qualcomm.com/product/publicresources/securitybulletin/june-2025-bulletin.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Jul 2025, 18:25 UTC

WeaknessesCWE-126

Technical details

References

Community reviews

Related threats