LiveActive security incident?Get immediate response
CVE Record

CVE-2018-14991: The Coolpad Defiant device with a build fingerprint of Coolpad/cp3632a/cp3632a:7.1.1/NMF26F/099480857:user/...

The Coolpad Defiant device with a build fingerprint of Coolpad/cp3632a/cp3632a:7.1.1/NMF26F/099480857:user/release-keys, the ZTE ZMAX Pro with a build fingerprint of ZTE/P895T20/urd:6.0.1/MMB29M/20170418.114928:user/release-keys, and the T-Mobile Revvl Plus with a build fingerprint of Coolpad/alchemy/alchemy:7.1.1/143.14.171129.3701A-TMO/buildf_nj_02-206:user/release-keys all contain a vulnerable, pre-installed Rich Communication Services (RCS) app. These devices contain an that app has a package name of com.suntek.mway.rcs.app.service (versionCode=1, versionName=RCS_sdk_M_native_20161008_01; versionCode=1, versionName=RCS_sdk_M_native_20170406_01) with an exported content provider named com.suntek.mway.rcs.app.service.provider.message.MessageProvider and a refactored version of the app with a package name of com.rcs.gsma.na.sdk (versionCode=1, versionName=RCS_SDK_20170804_01) with a content provider named com.rcs.gsma.na.provider.message.MessageProvider allow any app co-located on the device to read, write, insert, and modify the user's text messages. This is enabled by an exported content provider app component that serves as a wrapper to the official content provider that contains the user's text messages. This app cannot be disabled by the user and the attack can be performed by a zero-permission app.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Certain older carrier Android devices shipped with a pre-installed RCS messaging component that could let another app on the same phone access and alter text messages without requesting permissions. This affects the specific Coolpad Defiant, ZTE ZMAX Pro, and T-Mobile Revvl Plus builds named in the CVE source.

Executive priority

Prioritize this where affected devices still handle corporate SMS, authentication messages, customer communications, or regulated data. If these legacy models are absent from the fleet, business urgency is low.

Technical view

The vulnerable pre-installed RCS apps expose exported message content providers that wrap the system SMS provider. The CVE states a zero-permission co-located app can read, write, insert, and modify user text messages via those providers. No CVSS score, CWE, patch, or active exploitation evidence is provided in the source bundle.

Likely exposure

Exposure is limited to the specific listed device builds and RCS package versions. Organizations are most exposed where these legacy Android devices remain in use, especially BYOD or unmanaged fleets with third-party apps installed.

Exploitation context

The source describes local app-to-app abuse on the same device, not remote exploitation. KEV is false, and the bundle provides no cited evidence of active exploitation in the wild.

Researcher notes

The CVE record is specific but incomplete: severity, CVSS, CWE, and vendor remediation details are absent. Analysis should stay scoped to the named builds, package names, versions, and exported providers unless additional vendor evidence is obtained.

Mitigation direction

  • Inventory mobile fleets for the named device builds and RCS packages.
  • Check OEM, carrier, or MDM guidance for firmware updates or removal options.
  • Retire or isolate affected devices if no trusted update path exists.
  • Restrict installation of untrusted apps on affected or unmanaged devices.
  • Avoid using SMS for sensitive workflows on exposed devices.

Validation and detection

  • Confirm device model and build fingerprint match the CVE description.
  • Check whether the named RCS packages and versions are installed.
  • Verify whether the message content provider is exported on the device.
  • Review MDM inventory for unmanaged or legacy Android devices.
  • Confirm whether vendor or carrier updates are available and applied.
Prepared
Confidence
high
Sources
4

Public sources used

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-14991 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
4Source 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
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.