LiveActive security incident?Get immediate response
CVE Record

CVE-2017-18280: In Snapdragon (Automobile, Mobile, Wear) in version MDM9607, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD...

In Snapdragon (Automobile, Mobile, Wear) in version MDM9607, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 617, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SDM429, SDM439, SDM632, Snapdragon_High_Med_2016, when a Trusted Application has opened the SPI/I2C interface to a particular device, it is possible for another Trusted Application to read the data on this open interface by calling the SPI/I2C read function.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This Qualcomm Snapdragon issue can let one trusted application read data from an SPI/I2C hardware interface that another trusted application already opened. This may weaken confidentiality between trusted apps and attached devices on affected Snapdragon Automobile, Mobile, and Wear platforms. The public bundle does not provide CVSS, confirmed exploitation, or detailed remediation beyond vendor bulletin references. Exposure is most likely in devices using the listed Snapdragon Automobile, Mobile, or Wear platforms, including MDM9607, MSM8909W, MSM8996AU, SD 205 through SD 835, SDM429, SDM439, SDM632, and Snapdragon_High_Med_2016. Product-level impact depends on OEM firmware and security update status. Treat this as a firmware supply-chain exposure check rather than an emergency based on current evidence. Prioritize affected high-value or unsupported devices, especially where trusted applications may handle sensitive sensor, peripheral, or device data. Business urgency rises if an OEM cannot confirm patched firmware. Mitigation focus: Check Qualcomm and OEM security bulletins for CVE-2017-18280 guidance.; Apply OEM firmware or Android security updates that include the Qualcomm closed-source component fix.; Inventory devices using the affected Snapdragon platforms listed in the CVE..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2017-18280 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Automobile, Snapdragon Mobile, Snapdragon WearMDM9607, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 617, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SDM429, SDM439, SDM632, Snapdragon_High_Med_2016Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.