# CVE-2017-3762: Hardcoded credentials in Lenovo Fingerprint Manager Pro

> Local attackers can access sensitive Windows credentials and fingerprint data due to weak encryption and hard-coded passwords in Lenovo Fingerprint Manager Pro.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4pq3-x47m-6w2q

## What is CVE-2017-3762?

CVE-2017-3762 is a high-severity vulnerability in Lenovo Fingerprint Manager Pro, published on 26 Jan 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sensitive data stored by Lenovo Fingerprint Manager Pro, version 8.01.86 and earlier, including users' Windows logon credentials and fingerprint data, is encrypted using a weak algorithm, contains a hard-coded password, and is accessible to all users with local non-administrative access to the system in which it is installed.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Lenovo Fingerprint Manager Pro.

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

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

## Is CVE-2017-3762 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3762 is a high-severity vulnerability in Lenovo Fingerprint Manager Pro, published on 26 Jan 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-3762 in the wild and no public exploit code.

Affected product: Lenovo Fingerprint Manager Pro. 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-3762/ (Markdown: https://insights.sbomify.com/CVE-2017-3762/index.md)
```

## Sources

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

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