CVE-2018-17500
First published: Mon Mar 04 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 hardcoded OAuth Creds in plaintext. An attacker could exploit this vulnerability to obtain 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-17500?
CVE-2018-17500 is classified as a medium severity vulnerability due to the potential exposure of sensitive information.
How do I fix CVE-2018-17500?
To fix CVE-2018-17500, update Envoy Passport to the latest version where this issue has been addressed.
What types of devices are affected by CVE-2018-17500?
CVE-2018-17500 affects Envoy Passport for Android and iPhone with specific versions 2.2.5 and 2.4.0.
What type of information may be exposed due to CVE-2018-17500?
CVE-2018-17500 may expose hardcoded OAuth credentials stored in plaintext.
Can CVE-2018-17500 be exploited remotely?
CVE-2018-17500 requires local access to the device, thus it cannot be exploited remotely.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/author
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/tags
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- vendor/envoy
- canonical/envoy passport
- version/envoy passport/2.2.5
- version/envoy passport/2.4.0