Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storin…

published 2019-03-19 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-9252

cvss: 2.9; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits: 0; none known

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.

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.0	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
CNA	3.0	2.9	CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD	3.0	5.5	CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

Envoy Envoy Passport for iPhone
Envoy Envoy Passport for Android

Classification

Weakness

CWE-312 Cleartext Storage of Sensitive Information
CWE-532 Insertion of Sensitive Information into Log File

References

exchange.xforce.ibmcloud.com /vulnerabilities/149659
vdb-entry, third-party-advisory

Sources

CVE List CVE-2018-17499
NVD CVE-2018-17499

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary