dbcve.org
PassportApplication · Envoy

CVE-2018-17500

HIGH · 7.8 CVSS v3.0 Published 2019-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
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.

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 confidence

Envoy Passport for Android and iPhone stores hardcoded OAuth credentials in plaintext within the application binary. A local attacker with access to the device or the decompiled app can extract these credentials to impersonate users or access protected resources.

MitigationRemove all hardcoded credentials from the application source code, implement secure credential storage using platform-specific mechanisms (Android Keystore, iOS Keychain), and rotate any exposed OAuth credentials.

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
PassportApplication
Affected:= 2.2.5= 2.4.0

CVSS 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
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Envoy Passport installation
    Locate the Envoy Passport application on Android (APK file) or iOS (IPA file). On Android, check /data/app/ or use an APK extractor. On iOS, check for the IPA through backup or jailbreak tools.
    Affected if The Envoy Passport app (APK or IPA) is present on the device or in your build artifacts
  2. Determine installed version
    For Android APK, use 'aapt dump badging <apk>' and check the versionName and versionCode fields. For iOS IPA, extract the Info.plist and look for CFBundleShortVersionString.
    Affected if The version is exactly 2.2.5 or exactly 2.4.0
  3. Extract readable strings from binary
    Run 'strings' command on the APK (lib/armeabi-v7a/libenvoy.so or classes.dex) or iOS binary. Filter for OAuth-related terms: 'client_id', 'client_secret', 'access_token', 'oauth', 'bearer'.
    Affected if Plaintext OAuth-related strings are present in the binary
  4. Search for hardcoded credential patterns
    Inspect the extracted strings for patterns matching OAuth client IDs (typically 20-40 character alphanumeric) and client secrets. Use grep for 'client_secret=' or look for long random strings near OAuth endpoints.
    Affected if Hardcoded credential values (client IDs, secrets, tokens) are found in plaintext within the binary
  5. Decompile and verify credential storage
    Decompile the Android APK (using jadx or apktool) or reverse the iOS binary. Navigate to network/auth configuration files and verify if credentials are stored in source code or configuration files rather than retrieved from secure storage.
    Affected if Credentials are found hardcoded in source code or configuration files rather than retrieved from Android Keystore or iOS Keychain

Your environment is affected if Envoy Passport version 2.2.5 or 2.4.0 is installed and hardcoded OAuth credentials are present in the application binary.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove all hardcoded credentials from the application source code, implement secure credential storage using platform-specific mechanisms (Android Keystore, iOS Keychain), and rotate any exposed OAuth credentials.

Fix this in Passport Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-17500 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-17500 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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