CVE-2024-45569: Qualcomm Snapdragon · Improper Validation of Array Index
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% 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:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Feb 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-45569, organizations should: 1) Monitor Qualcomm and device vendors for official patches and apply them promptly once released. 2) Implement network segmentation and firewall rules to restrict exposure of vulnerable devices to untrusted networks, especially blocking unsolicited ML IE frame traffic. 3) Employ intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics targeting anomalous ML IE frame parsing or memory corruption attempts. 4) For enterprise mobile devices, enforce mobile device management (MDM) policies that limit installation of untrusted applications and control network access. 5) Collaborate with vendors to obtain firmware updates for embedded and IoT devices using affected Qualcomm platforms. 6) Conduct regular security assessments and penetration testing focusing on wireless protocol vulnerabilities. 7) Educate security teams about this vulnerability to enhance monitoring and incident response readiness. These steps go beyond generic advice by emphasizing network-level controls, vendor coordination, and proactive detection tailored to the specific nature of the vulnerability.
Description
Memory corruption while parsing the ML IE due to invalid frame content.