Skip to main content
CVE-2023-33014VulnerabilityPublished Updated

CVE-2023-33014: Qualcomm Snapdragon · Improper Input Validation

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.6 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

AI-suggested

Mitigation should focus on immediate risk reduction and long-term remediation. Organizations should: 1) Inventory and identify all devices using affected Qualcomm Snapdragon chipsets to understand exposure. 2) Limit physical access to vulnerable devices, especially in public or semi-public environments, to reduce attack surface given the physical proximity requirement. 3) Monitor network traffic for anomalous Diag command activity, employing advanced endpoint detection and response (EDR) tools capable of recognizing unusual diagnostic commands or device behavior. 4) Engage with device manufacturers and Qualcomm for firmware updates or patches addressing CVE-2023-33014 and apply them promptly once available. 5) For critical systems, consider network segmentation and device isolation to prevent lateral movement if exploitation occurs. 6) Educate staff on the risks of unauthorized device access and implement strict device usage policies. 7) Where possible, disable or restrict Diag command interfaces on devices not requiring diagnostic access in operational environments. These steps go beyond generic patching advice by emphasizing access control, monitoring, and proactive device management tailored to the vulnerability's characteristics.

Description

Information disclosure in Core services while processing a Diag command.

References

Community reviews

Loading reviews…