LiveActive security incident?Get immediate response
CVE Record

CVE-2017-14887: In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux ker...

In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, in the processing of messages of type eWNI_SME_MODIFY_ADDITIONAL_IES, an integer overflow leading to heap buffer overflow may potentially occur.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2017-14887 is a memory corruption issue in Qualcomm CAF Android-related WLAN code. A specific message-processing path can overflow an integer and then overflow heap memory. The public bundle does not provide severity, CVSS, affected device models, or confirmed exploitation evidence.

Executive priority

Prioritize this for mobile and embedded Android fleets where Qualcomm CAF-based firmware is present. Urgency depends on device exposure and patch status because public severity and exploitation evidence are missing from the supplied sources.

Technical view

The flaw is described in Android for MSM, Firefox OS for MSM, QRD Android, and CAF Android releases using the Linux kernel. Processing eWNI_SME_MODIFY_ADDITIONAL_IES messages may trigger an integer overflow leading to heap buffer overflow. The referenced CodeAurora commit and Pixel March 2018 bulletin are the available fix indicators.

Likely exposure

Exposure is most plausible in Android-derived devices using affected Qualcomm CAF/MSM WLAN components, especially builds aligned with qcacld-3.0 before the referenced fix. The bundle does not identify specific OEM devices, chipsets, Android versions, or deployed firmware packages.

Exploitation context

The bundle does not cite public exploitation, proof-of-concept activity, or CISA KEV listing. Treat this as a potential device-side memory corruption risk, but do not claim active exploitation from the provided evidence.

Researcher notes

Key evidence gaps are CVSS, CWE mapping, exact affected chipsets, attack preconditions, and OEM firmware status. The best validation path is source or firmware lineage review against the referenced CodeAurora commit and vendor bulletins.

Mitigation direction

  • Check OEM or vendor firmware guidance for CVE-2017-14887 coverage.
  • Apply Android, Pixel, or OEM security updates that include the March 2018 fixes.
  • For CAF-based builds, verify the referenced CodeAurora fix is incorporated.
  • Prioritize unsupported or unpatched Qualcomm-based Android device fleets for replacement planning.

Validation and detection

  • Inventory Android-derived devices using Qualcomm CAF/MSM WLAN components.
  • Check device security patch levels against the March 2018 Pixel bulletin where applicable.
  • Review source manifests or vendor release notes for the referenced CodeAurora commit.
  • Confirm unsupported devices are isolated or retired if no vendor fix is available.
Prepared
Confidence
medium
Sources
4

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-14887 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
n/an/an/aListed
Weakness

CWE details

No CWE listed

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