Security readout for executives and security teams
Plain-English summary
CVE-2021-35072 is a high-severity Qualcomm Snapdragon flaw in diagnostic command handling. A low-privileged local attacker could potentially trigger a buffer overflow with high confidentiality, integrity, and availability impact. The source bundle does not show public exploitation or KEV listing.
Executive priority
Treat this as a high-priority firmware and device-fleet exposure review, especially for embedded, mobile, IoT, and automotive deployments where patching cycles are slow.
Technical view
The issue is improper validation of an array index while processing an external DIAG command. CVSS 3.1 is 7.8 with local attack vector, low complexity, low privileges, no user interaction, unchanged scope, and high CIA impact.
Likely exposure
Exposure is likely in devices using the listed Qualcomm Snapdragon Auto, Mobile, IoT, Voice and Music, and Wearables chipsets. Risk depends on whether affected firmware is present and whether diagnostic command paths are reachable in production.
Exploitation context
The provided sources do not indicate active exploitation. The CVSS vector supports local exploitation by a low-privileged actor without user interaction, but the bundle does not provide exploit details or real-world attack evidence.
Researcher notes
The source bundle identifies broad chipset families but no CWE, exploit proof, or patch mechanics. Validate exposure through firmware lineage, OEM bulletins, and diagnostic interface accessibility rather than assuming every product using these chips is exploitable.
Mitigation direction
- Check Qualcomm’s May 2022 security bulletin and OEM firmware advisories for applicable updates.
- Apply vendor or device-maker firmware updates that address CVE-2021-35072.
- Limit access to diagnostic interfaces in production environments where operationally possible.
- Prioritize managed mobile, IoT, automotive, and embedded fleets using listed chipsets.
Validation and detection
- Inventory devices and modules containing the listed Qualcomm chipsets.
- Map firmware versions against Qualcomm and OEM advisories for CVE-2021-35072.
- Confirm whether DIAG interfaces are enabled or reachable on production builds.
- Prioritize assets where local low-privileged users or apps can access diagnostics.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-35072 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.qualcomm.com/company/product-security/bulletins/may-2022-bulletinCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
