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

> A malicious app can read scanned documents via the ContentProvider in the Epson iPrint Android application.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wx7r-grcc-7rrf

## What is CVE-2018-14902?

CVE-2018-14902 is a high-severity vulnerability in n/a, published on 30 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ContentProvider in the EPSON iPrint application 6.6.3 for Android does not properly restrict data access. This allows an attacker's application to read scanned documents.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Epson Iprint.

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

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

## Is CVE-2018-14902 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-14901](https://insights.sbomify.com/CVE-2018-14901/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14902 is a high-severity vulnerability in n/a, published on 30 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-14902 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-14902/ (Markdown: https://insights.sbomify.com/CVE-2018-14902/index.md)
```

## Sources

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

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