CVE-2024-53011: Qualcomm Snapdragon · Permissions, Privileges, and Access Controls
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 7.9 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Mar 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.
What to do
AI-suggested
To mitigate CVE-2024-53011 effectively, organizations should: 1) Monitor Qualcomm’s security advisories closely and apply official patches or firmware updates as soon as they become available to address the improper access controls in the Video Analytics engine. 2) Implement strict access control policies limiting which processes and users have high privilege access to the Video Analytics engine and related components, minimizing the risk of privilege misuse. 3) Employ runtime monitoring and anomaly detection on devices to identify unusual access patterns or attempts to access video analytics data beyond authorized scopes. 4) For device manufacturers and integrators, conduct thorough security reviews and testing of access control mechanisms in embedded components, especially those handling sensitive data like video analytics. 5) Use hardware-based security features such as Trusted Execution Environments (TEE) or secure enclaves to isolate sensitive processing and restrict access to video analytics data. 6) Educate administrators and users about the risks of privilege escalation and enforce the principle of least privilege in device management. 7) In environments where patching is delayed, consider network segmentation and limiting physical or local access to vulnerable devices to reduce exploitation chances. 8) Collaborate with Qualcomm and security communities to share threat intelligence and best practices for securing affected platforms.
Description
Information disclosure may occur due to improper permission and access controls to Video Analytics engine.