CVE-2018-17499
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEnvoy 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceEnvoy Passport mobile apps for Android and iPhone store unencrypted sensitive data (including API keys and tokens) in application logs, allowing a local attacker with device access to extract these credentials by reading the log files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.2.5= 2.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Envoy Passport mobile app is installedOn Android: Open Settings > Apps and look for 'Envoy Passport' in the app list, or use ADB command: 'adb shell pm list packages | grep envoy'. On iOS: Go to Settings > General > iPhone Storage and search for 'Envoy Passport', or check the app list on the home screen.Affected if The Envoy Passport app is present on the device
-
Determine installed app version on AndroidOpen Google Play Store app, search for 'Envoy Passport', tap on the app, and scroll to view the version under 'Additional information'. Alternatively, use ADB: 'adb shell dumpsys package com.envoy.passport' and look for 'versionName' in the output.Affected if The version listed is exactly 2.2.5 or 2.4.0
-
Determine installed app version on iOSOpen the App Store app, search for 'Envoy Passport', tap on the app, and view the version information displayed below the app name. Alternatively, open the app in Xcode device organizer or check via iTunes/Finder when device is connected.Affected if The version listed is exactly 2.2.5 or 2.4.0
-
Inspect application log files for sensitive dataOn Android: Use ADB to pull logs with 'adb logcat -d' or access log files directly via 'adb shell run-as com.envoy.passport ls files/'. On iOS: Connect device to computer, open Xcode > Devices and Simulators > View Device Logs, or use iMazing/iTools to access app container logs.Affected if Log output contains API keys, authentication tokens, bearer tokens, or other credential-like strings in plain text
A user is affected if they have Envoy Passport app version 2.2.5 or 2.4.0 installed on their Android or iOS device and the application logs contain unencrypted sensitive credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove sensitive data from all logging statements, implement log sanitization, or use encrypted/sensitive-data-excluding logging mechanisms to prevent credential exposure.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17499 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-17499 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data