# CVE-2019-14339: Information disclosure in n/a

> A malicious Android app can exploit a ContentProvider flaw in Canon PRINT to steal sensitive credentials like admin passwords and Wi-Fi keys.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mc8r-fh77-9634

## What is CVE-2019-14339?

CVE-2019-14339 is a medium-severity vulnerability in n/a, published on 5 Sep 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The ContentProvider in the Canon PRINT jp.co.canon.bsd.ad.pixmaprint 2.5.5 application for Android does not properly restrict canon.ij.printer.capability.data data access. This allows an attacker's malicious application to obtain sensitive information including factory passwords for the administrator web interface and WPA2-PSK key.

## Which versions are affected by CVE-2019-14339?

It affects 1 product.


Products: Canon Print.

## How do I fix CVE-2019-14339?

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

## Is CVE-2019-14339 being exploited?

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

Public exploit code:

- POC for CVE-2019-14339 Canon PRINT 2.5.5 (github_poc): https://github.com/0x48piraj/CVE-2019-14339
- Canon PRINT 2.5.5 - Information Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14339 and fix it if it is affected.

What it is: CVE-2019-14339 is a medium-severity vulnerability in n/a, published on 5 Sep 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-14339 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-2019-14339/ (Markdown: https://insights.sbomify.com/CVE-2019-14339/index.md)
```

## Sources

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

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