Security readout for executives and security teams
Plain-English summary
This is a low-severity mobile app secret handling issue. Specific Envoy Passport iPhone and Android versions reportedly stored hardcoded OAuth credentials in plaintext, which could expose sensitive information to a local attacker. The source bundle does not show active exploitation.
Executive priority
Treat as a low-priority mobile hygiene issue unless affected versions are deployed broadly or the OAuth credentials protect sensitive workflows. Prioritize inventory and vendor confirmation over emergency response.
Technical view
CVE-2018-17500 affects Envoy Passport for iPhone 2.2.5 and Android 2.4.0. The vulnerability is plaintext storage of hardcoded OAuth credentials. CVSS 3.0 is 2.9 with local attack vector, high complexity, no privileges, no user interaction, and confidentiality impact only.
Likely exposure
Exposure is most likely limited to endpoints or users still running Envoy Passport for iPhone 2.2.5 or Android 2.4.0. Organizations without those mobile app versions are unlikely to be affected based on the provided sources.
Exploitation context
The sources describe a local attacker obtaining sensitive information. They do not identify remote exploitation, public exploit use, or CISA KEV inclusion. Evidence is incomplete on practical exploitability and environmental prerequisites.
Researcher notes
The provided data is sparse: no CWE, no fixed version, and only one external vulnerability database reference. CVSS indicates confidentiality-only impact and local access. Avoid assuming affected Envoy products beyond the two named mobile apps.
Mitigation direction
- Inventory managed and BYOD devices for the affected Envoy Passport versions.
- Check Envoy or app-store guidance for a fixed release or retirement path.
- Update or remove affected app versions where vendor guidance supports it.
- Rotate exposed OAuth credentials only if vendor or internal evidence confirms exposure.
Validation and detection
- Confirm whether iPhone version 2.2.5 or Android version 2.4.0 is installed.
- Verify current app versions against vendor or app-store release guidance.
- Review mobile management records for remaining affected installs.
- Check authentication logs for unusual OAuth client behavior if credentials may be shared.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-17500 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 2.9 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/C:L/AC:H/I:N/AV:L/A:N/PR:N/UI:N/S:U/RL:O/E:U/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/C:L/AC:H/I:N/AV:L/A:N/PR:N/UI:N/S:U/RL:O/E:U/RC:C1.41.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
2.9LowVector: CVSS:3.0/C:L/AC:H/I:N/AV:L/A:N/PR:N/UI:N/S:U/RL:O/E:U/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- envoy-oauthcreds-cve201817500-info-disc (149660)CVE reference · vdb-entry, x_refsource_XF
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
