CVE-2017-9968
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 security misconfiguration vulnerability exists in Schneider Electric's IGSS Mobile application versions 3.01 and prior in which a lack of certificate pinning during the TLS/SSL connection establishing process can result in a man-in-the-middle attack.
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 · high confidenceThe IGSS Mobile application versions 3.01 and prior lacks certificate pinning during TLS/SSL connections, allowing an attacker to intercept communications between the mobile app and server via a man-in-the-middle attack. This security misconfiguration means the application does not validate that it is communicating with the legitimate server by pinning a specific certificate or public key.
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<= 3.01CVSS 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 IGSS Mobile installationCheck the mobile device (Android or iOS) for the presence of the IGSS Mobile application by reviewing installed apps or checking the APK/IPA file if you have access to the application package.Affected if The IGSS Mobile application is installed on any device in the environment.
-
Determine installed versionOn Android, check the app version in Google Play Store or by examining the APK file metadata. On iOS, check in the App Store or by examining the IPA file. Compare the version number to the affected range.Affected if The installed version is 3.01 or any prior version (e.g., 3.00, 2.x, 1.x).
-
Verify certificate pinning implementationPerform a man-in-the-middle test using a proxy (such as Burp Suite or OWASP ZAP) with a self-signed certificate. Attempt to intercept traffic between the IGSS Mobile app and its server. Observe whether the app rejects the untrusted certificate or accepts the connection.Affected if The application accepts the proxy certificate and establishes a connection, indicating certificate pinning is not implemented.
-
Analyze network traffic for certificate validationCapture network traffic using a packet sniffer while the app communicates with the server. Analyze whether the app validates the server certificate chain properly or accepts certificates from untrusted CAs.Affected if The app successfully communicates with the server even when presented with a certificate not signed by a trusted root CA, confirming lack of pinning.
A user is affected if IGSS Mobile version 3.01 or prior is installed and the application accepts connections through a man-in-the-middle proxy, indicating certificate pinning is not enforced.
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 certificate pinning in the mobile application to bind the server's expected certificate or public key, ensuring the app rejects connections to any server presenting a different certificate, combined with proper TLS/SSL configuration validation.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9968 — 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-9968 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