Read the docs
TI-2016-08211 Aliases CVE-2016-10135GHSA-j3c4-969x-5vx7

An issue was discovered on LG devices using the MTK chipset with L(5.0/5.1)…

Priority LOW 27CWE-200Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
No fix listed

Attack profile from CVSS 3.0 · NVD. Fix status from CNA. Impact type from CWE-200.

Summary

An issue was discovered on LG devices using the MTK chipset with L(5.0/5.1), M(6.0/6.0.1), and N(7.0) software, and RCA Voyager Tablet, BLU Advance 5.0, and BLU R1 HD devices. The MTKLogger app with a package name of com.mediatek.mtklogger has application components that are accessible to any application that resides on the device. Namely, the com.mediatek.mtklogger.framework.LogReceiver and com.mediatek.mtklogger.framework.MTKLoggerService application components are exported since they contain an intent filter, are not protected by a custom permission, and do not explicitly set the android:exported attribute to false. Therefore, these components are exported by default and are thus accessible to any third party application by using android.content.Intent object for communication. These application components can be used to start and stop the logs using Intent objects with embedded data. The available logs are the GPS log, modem log, network log, and mobile log. The base directory that contains the directories for the 4 types of logs is /sdcard/mtklog which makes them accessible to apps that require the READ_EXTERNAL_STORAGE permission. The GPS log contains the GPS coordinates of the user as well as a timestamp for the coordinates. The modem log contains AT commands and their parameters which allow the user's outgoing and incoming calls and text messages to be obtained. The network log is a tcpdump network capture. The mobile log contains the Android log, which is not available to third-party apps as of Android 4.1. The LG ID is LVE-SMP-160019.

Why it matters now

EPSS 0.00928 60th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
——all versions—No fix listedCNA
  • — Vendor— Affected all versions Fixed in — No fix listed CNA

CPE configurations NVD · 5

CPEVersionsRoleVendor
cpe:2.3:o:lg:lg_mobile:5.0:*:*:*:*:*:*:*5.0VulnerableLG
cpe:2.3:o:lg:lg_mobile:5.1:*:*:*:*:*:*:*5.1VulnerableLG
cpe:2.3:o:lg:lg_mobile:6.0:*:*:*:*:*:*:*6.0VulnerableLG
cpe:2.3:o:lg:lg_mobile:6.0.1:*:*:*:*:*:*:*6.0.1VulnerableLG
cpe:2.3:o:lg:lg_mobile:7.0:*:*:*:*:*:*:*7.0VulnerableLG
  • cpe:2.3:o:lg:lg_mobile:5.0:*:*:*:*:*:*:* Versions 5.0 Vulnerable ·LG
  • cpe:2.3:o:lg:lg_mobile:5.1:*:*:*:*:*:*:* Versions 5.1 Vulnerable ·LG
  • cpe:2.3:o:lg:lg_mobile:6.0:*:*:*:*:*:*:* Versions 6.0 Vulnerable ·LG
  • cpe:2.3:o:lg:lg_mobile:6.0.1:*:*:*:*:*:*:* Versions 6.0.1 Vulnerable ·LG
  • cpe:2.3:o:lg:lg_mobile:7.0:*:*:*:*:*:*:* Versions 7.0 Vulnerable ·LG

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2016-10135
  2. 2026-10-03 Alias added: GHSA-j3c4-969x-5vx7

References

Sources