LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13887: Untrusted header fields in GNSS XTRA3 function can lead to integer overflow in Snapdragon Auto, Snapdragon...

Untrusted header fields in GNSS XTRA3 function can lead to integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in MDM9150, MDM9206, MDM9607, MDM9635M, MDM9650, MDM9655, MSM8909W, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 600, SD 625, SD 632, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 835, SD 845 / SD 850, SDA660, SDM439, SDM630, SDM660, SDX20, SM7150, SXR1130

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-13887 is a Qualcomm Snapdragon GNSS issue where untrusted XTRA3 header data can cause an integer overflow. The public bundle lists many Snapdragon modem, mobile, IoT, auto, compute, and wearable chipsets. Severity, CVSS, and concrete business impact are not provided, so urgency depends on affected device presence and vendor patch status.

Executive priority

Do not treat this as a confirmed emergency from the provided evidence. Assign a vulnerability-management workstream to identify affected Qualcomm-based assets, verify OEM patch availability, and close visibility gaps in embedded and mobile fleets.

Technical view

The vulnerability is in Qualcomm's GNSS XTRA3 function. Untrusted header fields can lead to integer overflow on listed Snapdragon platforms and chipsets. The bundle does not specify memory corruption outcome, privilege context, attack path, CVSS, CWE, or exact fixed firmware versions.

Likely exposure

Exposure is most likely in devices using the listed Qualcomm Snapdragon chipsets and GNSS/XTRA3 functionality. This may include mobile, IoT, wearable, automotive, compute, and modem-based products. Asset owners need chipset and firmware visibility to determine relevance.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit availability, or exploitation details. Treat exploitation status as unconfirmed, not known-active.

Researcher notes

Evidence is limited to the CVE description and Qualcomm reference. The affected list is broad, but severity, exploitability, fixed versions, and precise impact are absent from the bundle. Further analysis should start with Qualcomm and OEM advisories.

Mitigation direction

  • Inventory products using the listed Qualcomm chipsets.
  • Check Qualcomm and OEM bulletins for fixed firmware or security updates.
  • Apply relevant OEM firmware updates through supported channels.
  • Prioritize managed fleets where GNSS/XTRA3 functionality is enabled.
  • Track unsupported devices for replacement or compensating controls.

Validation and detection

  • Map device models to Qualcomm chipset or modem identifiers.
  • Compare firmware levels against Qualcomm and OEM advisory guidance.
  • Confirm security update deployment through device management records.
  • Review SBOMs, procurement data, and vendor attestations for affected chipsets.
  • Document devices where patch status cannot be verified.
Prepared
Confidence
medium
Sources
3

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-2018-13887 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
2Source links

CVSS and timeline data

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon WearablesMDM9150, MDM9206, MDM9607, MDM9635M, MDM9650, MDM9655, MSM8909W, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 600, SD 625, SD 632, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 835, SD 845 / SD 850, SDA660, SDM439, SDM630, SDM660, SDX20, SM7150, SXR1130Listed
Weakness

CWE details

No CWE listed

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