# CVE-2017-9969: Hardcoded credentials in n/a

> Attackers can read sensitive passwords stored in clear text within the configuration file of the IGSS Mobile application.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rq73-574j-8g3v

## What is CVE-2017-9969?

CVE-2017-9969 is a medium-severity vulnerability in n/a, published on 12 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An information disclosure vulnerability exists in Schneider Electric's IGSS Mobile application version 3.01 and prior. Passwords are stored in clear text in the configuration which can result in exposure of sensitive information.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Schneider-Electric Igss Mobile.

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

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

## Is CVE-2017-9969 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9968](https://insights.sbomify.com/CVE-2017-9968/): Security feature bypass in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9969 is a medium-severity vulnerability in n/a, published on 12 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9969 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-9969/ (Markdown: https://insights.sbomify.com/CVE-2017-9969/index.md)
```

## Sources

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

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