LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13895: Due to the missing permissions on several content providers of the RCS app in its android manifest file wil...

Due to the missing permissions on several content providers of the RCS app in its android manifest file will lead to an unprivileged access to phone in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Wearables in MDM9150, MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 439 / SD 429, SD 450, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDA660, SDM439, SDM630, SDM660, SDX20

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Qualcomm issue concerns Android devices where the RCS app exposed content providers without required manifest permissions. That could let an unprivileged app access phone-related functionality or data that should have been protected. Business impact depends on the affected Snapdragon platform, OEM firmware, and whether the vulnerable RCS app is present.

Executive priority

Treat this as an inventory and vendor-patch verification item rather than an emergency unless affected, unpatched devices are widely deployed. The missing exploitation and severity data reduce certainty, but the affected platform list is broad enough to warrant tracking in mobile fleet risk reviews.

Technical view

CVE-2018-13895 is a missing-permission flaw in several RCS app content providers declared in the Android manifest. Qualcomm lists many Snapdragon Auto, Compute, Connectivity, IoT, Mobile, and Wearables platforms. The bundle provides no CVSS, CWE, CPEs, detailed impact boundaries, or patch version data.

Likely exposure

Most relevant exposure is Android-based devices using the listed Qualcomm Snapdragon platforms with the affected RCS app integration. Exposure cannot be confirmed from chipset alone because OEM firmware, carrier customizations, and app packaging determine whether the vulnerable component is present.

Exploitation context

The provided sources do not state active exploitation, and the CVE is not marked in KEV. The described access appears local to an unprivileged app interacting with improperly protected content providers. The bundle does not establish remote exploitability, public exploit availability, or required user interaction.

Researcher notes

Evidence is sparse. The public description identifies missing manifest permissions on RCS content providers but does not define the exact provider names, data exposed, privileges gained, or fixed builds. Validate only in controlled test environments and avoid assuming all listed chipsets are vulnerable in every OEM product.

Mitigation direction

  • Check Qualcomm and device OEM bulletins for the applicable firmware or security update.
  • Prioritize managed Android devices using the listed Snapdragon platforms.
  • Confirm whether the vulnerable RCS app is present on deployed device images.
  • Apply OEM-approved firmware, carrier, or system app updates when available.
  • Limit deployment of untrusted apps on potentially affected devices.

Validation and detection

  • Inventory device models and map them to the listed Qualcomm platforms.
  • Check OEM Android security bulletin status for CVE-2018-13895.
  • Confirm RCS app package presence and version on representative device builds.
  • Review the RCS app manifest for content providers lacking protective permissions.
  • Document devices where OEM guidance or patch status is unavailable.
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-13895 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 IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon WearablesMDM9150, MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 439 / SD 429, SD 450, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDA660, SDM439, SDM630, SDM660, SDX20Listed
Weakness

CWE details

No CWE listed

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