# CVE-2018-14995: Information disclosure in n/a > A pre-installed ZTE app allows any third-party app to enable and read sensitive modem and logcat logs containing SMS and call data. - **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 28 Dec 2018 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-mh7p-2p63-76h2 ## What is CVE-2018-14995? CVE-2018-14995 is a medium-severity vulnerability in n/a, published on 28 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description The ZTE Blade Vantage Android device with a build fingerprint of ZTE/Z839/sweet:7.1.1/NMF26V/20180120.095344:user/release-keys, the ZTE Blade Spark Android device with a build fingerprint of ZTE/Z971/peony:7.1.1/NMF26V/20171129.143111:user/release-keys, the ZTE ZMAX Pro Android device with a build fingerprint of ZTE/P895T20/urd:6.0.1/MMB29M/20170418.114928:user/release-keys, and the ZTE ZMAX Champ Android device with a build fingerprint of ZTE/Z917VL/fortune:6.0.1/MMB29M/20170327.120922:user/release-keys contain a pre-installed platform app with a package name of com.android.modem.service (versionCode=25, versionName=7.1.1; versionCode=23, versionName=6.0.1) that exports an interface to any app on co-located on the device. Using the exported interface of the com.android.modem.service app, any app can enable and obtain certain log files (modem and logcat) without the appropriate corresponding access permissions. The modem logs contain the phone number and full text body of incoming and outgoing text messages in binary format. In addition, the modem log contains the phone numbers for both incoming and outgoing phone calls. The system-wide logcat logs (those obtained via the logcat binary) tend to contain sensitive user data. Third-party apps are prevented from directly reading the system-wide logcat logs. The capability to read from the system-wide logcat logs is only available to pre-installed system apps and platform apps. The modem log and/or logcat log, once activated, get written to external storage (SD card). An app aware of this vulnerability can enable the logs, parse them for relevant data, and exfiltrate them from the device. The modem log and logcat log are inactive by default, but a third-party app with no permissions can activate them, although the app will need to be granted the READ_EXTERNAL_STORAGE permission to access them. Weakness: CWE-532 (Insertion of Sensitive Information into Log File) ## Which versions are affected by CVE-2018-14995? It affects 4 products. Products: Zteusa Zte Blade Spark Firmware, Zteusa Zte Blade Vantage Firmware, Zteusa Zte Zmax Champ Firmware, Zteusa Zte Zmax Pro Firmware. ## How do I fix CVE-2018-14995? No fix has been published for CVE-2018-14995 yet. Limit exposure of the affected software until one is available. ## Is CVE-2018-14995 being exploited? There is no known exploitation of CVE-2018-14995 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-14995 and fix it if it is affected. What it is: CVE-2018-14995 is a medium-severity vulnerability in n/a, published on 28 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2018-14995 in the wild and no public exploit code. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2018-14995/ (Markdown: https://insights.sbomify.com/CVE-2018-14995/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-14995 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-14995 - OSV: https://osv.dev/vulnerability/CVE-2018-14995 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-14995/ Summaries are generated and may contain mistakes; the official description above is the record.