# CVE-2017-9968: Security feature bypass in n/a

> Attackers can intercept traffic via man-in-the-middle attacks due to missing certificate pinning in the IGSS Mobile application.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-w8xw-59hx-9h9r

## What is CVE-2017-9968?

CVE-2017-9968 is a medium-severity vulnerability in n/a, published on 12 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A 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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2017-9968?

It affects 1 product.


Products: Schneider-Electric Igss Mobile.

## How do I fix CVE-2017-9968?

No fix has been published for CVE-2017-9968 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-9968 being exploited?

There is no known exploitation of CVE-2017-9968 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-9969](https://insights.sbomify.com/CVE-2017-9969/): Hardcoded credentials in n/a (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9968 and fix it if it is affected.

What it is: CVE-2017-9968 is a medium-severity vulnerability in n/a, published on 12 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9968 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-9968/ (Markdown: https://insights.sbomify.com/CVE-2017-9968/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9968
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9968
- OSV: https://osv.dev/vulnerability/CVE-2017-9968

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9968/
Summaries are generated and may contain mistakes; the official description above is the record.