# CVE-2018-17499: Information disclosure in Envoy Passport for Android

> A local attacker can obtain sensitive API keys and tokens from unencrypted logs in Envoy Passport mobile applications.

- **Severity:** Low 2.9 (`CVSS:3.0/AC:H/C:L/I:N/PR:N/A:N/AV:L/S:U/UI:N/RC:C/E:U/RL:O`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mjr4-9rv8-9g3f

## What is CVE-2018-17499?

CVE-2018-17499 is a low-severity vulnerability in Envoy Passport for Android, published on 19 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storing of unencrypted data in logs. An attacker could exploit this vulnerability to obtain two API keys, a token and other sensitive information.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Envoy Passport.

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

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

## Is CVE-2018-17499 being exploited?

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

## Other vulnerabilities in Envoy Passport for Android

- [CVE-2018-17500](https://insights.sbomify.com/CVE-2018-17500/): Hardcoded credentials in Envoy Passport for Android (low 2.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17499 is a low-severity vulnerability in Envoy Passport for Android, published on 19 Mar 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-17499 in the wild and no public exploit code.

Affected product: Envoy Passport for Android. 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-17499/ (Markdown: https://insights.sbomify.com/CVE-2018-17499/index.md)
```

## Sources

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

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