CVE-2018-17499
First published: Tue Mar 19 2019(Updated: )
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.
Credit: psirt@us.ibm.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Envoy Passport | =2.2.5 | |
| Envoy Passport | =2.4.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-17499?
CVE-2018-17499 is considered to have a high severity due to the potential exposure of sensitive information.
How do I fix CVE-2018-17499?
To fix CVE-2018-17499, ensure that logs do not store unencrypted sensitive information and update to the latest versions of Envoy Passport.
What versions are affected by CVE-2018-17499?
CVE-2018-17499 affects Envoy Passport for iPhone version 2.2.5 and Envoy Passport for Android version 2.4.0.
What type of information is exposed in CVE-2018-17499?
CVE-2018-17499 can expose sensitive information such as two API keys and a token.
Who can exploit CVE-2018-17499?
CVE-2018-17499 can be exploited by local attackers who have access to the logs containing unencrypted data.
- collector/nvd-index
- agent/weakness
- agent/type
- agent/softwarecombine
- agent/author
- agent/references
- agent/severity
- agent/tags
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- vendor/envoy
- canonical/envoy passport
- version/envoy passport/2.2.5
- version/envoy passport/2.4.0