CVE-2017-12697
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 · uneditedA Man-in-the-Middle 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 intercept sensitive information when the client connects to the server.
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 confidenceA Man-in-the-Middle vulnerability in the GM and Shanghai OnStar SOS iOS Client 7.1 allows attackers on the same network to intercept sensitive information transmitted between the client and server, likely due to improper SSL/TLS certificate validation or lack of certificate pinning.
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= 7.1CVSS 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/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.
-
Identify if GM Shanghai OnStar iOS app is installedCheck the iOS device for the presence of the 'OnStar' or 'Shanghai OnStar' application in the installed apps list. This can be done through Settings > General > iPhone Storage (or Device Management on older iOS versions), or by searching for the app on the home screen.Affected if The GM Shanghai OnStar iOS client application is installed on the device
-
Determine the installed version of the OnStar appOpen the App Store app, search for 'OnStar' or 'Shanghai OnStar', tap on the app, and scroll to the Version Information section. Alternatively, in iOS, go to Settings > General > iPhone Storage, find the OnStar app, and view the version number displayed.Affected if The installed version is exactly 7.1
-
Verify if the app transmits sensitive data over networkUse a network traffic analysis tool (such as a proxy or network sniffer) to inspect traffic between the OnStar app and its servers. Look for connections transmitting personal or vehicle-related information.Affected if The app sends sensitive personal or vehicle data over unencrypted or improperly validated connections
-
Test for certificate validation weaknessesConfigure a proxy with a self-signed certificate and attempt to intercept traffic from the OnStar app. If the app accepts the proxy certificate without warning or failure, this indicates weak or absent certificate validation.Affected if The app accepts connections through a proxy with an untrusted certificate, indicating improper SSL/TLS validation or lack of certificate pinning
The environment is affected if the GM Shanghai OnStar iOS Client version 7.1 is installed and the app accepts connections with improper SSL/TLS certificate validation or lacks certificate pinning, allowing intercepted sensitive information.
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 dataImplement proper certificate validation and certificate pinning in the iOS client to ensure secure connections to the server and prevent MitM attacks.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12697 — 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-2017-12697 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