Skip to main content
VulnerabilityPublished Updated

CVE-2023-33070: Qualcomm Snapdragon · Improper Authentication

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Dec 2023

  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 26 Oct 2026.

What to do

AI-suggested

  1. Immediate inventory and identification of all Qualcomm Snapdragon-based devices and platforms within the organization, focusing on automotive OS and embedded systems.
  2. Engage with Qualcomm and device vendors to obtain and apply security patches or firmware updates as soon as they become available.
  3. Implement strict access controls and network segmentation to limit local access to vulnerable devices, reducing the risk of exploitation since the attack vector is local.
  4. Monitor device logs and system behavior for signs of transient DoS or unusual disruptions in secure IO operations.
  5. For automotive systems, integrate fail-safe mechanisms that maintain critical functions even during transient DoS conditions to mitigate safety risks.
  6. Collaborate with suppliers to ensure secure update mechanisms are in place for embedded devices to facilitate timely patch deployment.
  7. Conduct penetration testing and security assessments focusing on local access vectors to identify potential exploitation paths.
  8. Educate technical teams about the vulnerability specifics to enhance detection and response capabilities.
  9. Consider deploying runtime protection or anomaly detection tools that can identify and block unauthorized secure IO calls.
  10. Maintain up-to-date asset management and vulnerability scanning to track affected hardware and firmware versions continuously.

Description

Transient DOS in Automotive OS due to improper authentication to the secure IO calls.

References

Community reviews

Loading reviews…