LiveActive security incident?Get immediate response
CVE Record

CVE-2018-11928: Lack of check on length parameter may cause buffer overflow while processing WMI commands in Snapdragon Aut...

Lack of check on length parameter may cause buffer overflow while processing WMI commands in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in IPQ8074, MDM9206, MDM9607, MDM9640, MDM9650, MSM8996AU, QCA6174A, QCA6564, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA8081, QCA9377, QCA9379, QCA9886, QCS605, SD 210/SD 212/SD 205, SD 425, SD 600, SD 625, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM630, SDM660, SDX20, SDX24, SM7150, SXR1130

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This issue affects many Qualcomm Snapdragon chip families used across mobile, IoT, automotive, networking, and connected devices. A missing length check while handling WMI commands could cause a buffer overflow. The public bundle does not provide severity, exploit requirements, or device model names, so urgency depends on whether your assets contain the listed Qualcomm chips.

Executive priority

Make this an inventory and vendor-follow-up priority, not an emergency exploitation response based on current evidence. The affected Qualcomm footprint is broad, but missing severity and exploit data means business urgency should be driven by asset criticality and vendor patch availability.

Technical view

CVE-2018-11928 is a Qualcomm Snapdragon buffer overflow condition caused by inadequate validation of a length parameter during WMI command processing. The affected list spans multiple Snapdragon product lines and chipsets. The source bundle provides no CVSS score, CWE mapping, attack vector, privilege requirement, patch state, or affected firmware version detail.

Likely exposure

Organizations may be exposed through devices using the listed Qualcomm chipsets, including embedded, mobile, wireless, networking, IoT, and automotive platforms. Exposure cannot be confirmed from product names alone; it requires hardware and firmware inventory mapping to the affected Qualcomm parts.

Exploitation context

The CVE is not listed as KEV in the provided bundle. No cited source in the bundle reports active exploitation, public exploit availability, or exploitation prerequisites. Treat exploitation status as unconfirmed rather than absent.

Researcher notes

Evidence only confirms a missing length check causing buffer overflow during WMI command processing across listed Qualcomm products and chipsets. The bundle lacks CVSS, CWE, exact firmware versions, exploitability conditions, remediation details, and active exploitation evidence. Avoid assumptions beyond chipset-level exposure.

Mitigation direction

  • Map hardware inventory to the affected Qualcomm chipset list.
  • Check Qualcomm and OEM advisories for CVE-2018-11928 guidance.
  • Apply vendor-approved firmware or security updates when available.
  • Track unsupported devices that contain affected chipsets.
  • Prioritize internet-facing, unmanaged, or safety-relevant embedded assets.

Validation and detection

  • Confirm chipsets through BOMs, MDM data, procurement records, or vendor documentation.
  • Review OEM firmware release notes for CVE-2018-11928 coverage.
  • Identify devices with affected chipsets and no available vendor fix.
  • Record ownership and operational criticality for affected assets.
  • Monitor Qualcomm and OEM bulletins for updated remediation details.
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-11928 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 Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and NetworkingIPQ8074, MDM9206, MDM9607, MDM9640, MDM9650, MSM8996AU, QCA6174A, QCA6564, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA8081, QCA9377, QCA9379, QCA9886, QCS605, SD 210/SD 212/SD 205, SD 425, SD 600, SD 625, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM630, SDM660, SDX20, SDX24, 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.