CVE-2017-12695 json
An Improper Authentication issue was discovered in General Motors (GM) and Shanghai OnStar (SOS) SOS iOS Client 7.1.
published 2018-01-09 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-4234
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
An Improper Authentication issue was discovered in General Motors (GM) and Shanghai OnStar (SOS) SOS iOS Client 7.1. Successful exploitation of this vulnerability may allow an attacker to subvert security mechanisms and reset a user account password.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-17-234-04 updated cvss 8.8
General Motors and Shanghai OnStar (SOS) iOS Client
-
General Motors (GM), Shanghai OnStar (SOS) Shanghai OnStar iOS Client 7.1affected: mitigation “Users should not root or jailbreak their phones to prevent the preconditions for attacker access to mobile phone memory, including the ability to read JSON web token encryption keys.”
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
1.85% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
Affected products
- n/a General Motors and Shanghai OnStar (SOS) iOS Client
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
ics-cert.us-cert.gov
/advisories/ICSA-17-234-04
mitigation, third-party-advisory, us-government-resource
-
securityfocus.com
/bid/102481
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-12695
- NVD CVE-2017-12695
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.