# CVE-2018-14980: Information disclosure in n/a

> Malicious apps can force screenshots of sensitive notifications, including 2FA codes, even when the device is locked, due to a modified Android system component.

- **Severity:** High 7.1 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 25 Apr 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c6g2-p9rv-24xp

## What is CVE-2018-14980?

CVE-2018-14980 is a high-severity vulnerability in n/a, published on 25 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ASUS ZenFone 3 Max Android device with a build fingerprint of asus/US_Phone/ASUS_X008_1:7.0/NRD90M/US_Phone-14.14.1711.92-20171208:user/release-keys contains the android framework (i.e., system_server) with a package name of android (versionCode=24, versionName=7.0) that has been modified by ASUS or another entity in the supply chain. The system_server process in the core android package has an exported broadcast receiver that allows any app co-located on the device to programmatically initiate the taking of a screenshot and have the resulting screenshot be written to external storage (i.e., sdcard). The taking of a screenshot is not transparent to the user; the device has a screen animation as the screenshot is taken and there is a notification indicating that a screenshot occurred. If the attacking app also requests the EXPAND_STATUS_BAR permission, it can wake the device up using certain techniques and expand the status bar to take a screenshot of the user's notifications even if the device has an active screen lock. The notifications may contain sensitive data such as text messages used in two-factor authentication. The system_server process that provides this capability cannot be disabled, as it is part of the Android framework. The notification can be removed by a local Denial of Service (DoS) attack to reboot the device.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2018-14980?

It affects 1 product.


Products: Asus Zenfone 3 Max Firmware.

## How do I fix CVE-2018-14980?

No fix has been published for CVE-2018-14980 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-14980 being exploited?

There is no known exploitation of CVE-2018-14980 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-14993](https://insights.sbomify.com/CVE-2018-14993/): Privilege escalation in n/a (high 7.8)
- [CVE-2018-14992](https://insights.sbomify.com/CVE-2018-14992/): Missing authorization in n/a (medium 5.5)
- [CVE-2018-14979](https://insights.sbomify.com/CVE-2018-14979/): Information disclosure in n/a (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14980 and fix it if it is affected.

What it is: CVE-2018-14980 is a high-severity vulnerability in n/a, published on 25 Apr 2019. 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-14980 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-14980/ (Markdown: https://insights.sbomify.com/CVE-2018-14980/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-14980
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-14980
- OSV: https://osv.dev/vulnerability/CVE-2018-14980

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-14980/
Summaries are generated and may contain mistakes; the official description above is the record.