# CVE-2017-3742: Information disclosure in Lenovo Connect2

> Attackers with local read access can retrieve ad-hoc connection passwords to intercept file transfers in Lenovo Connect2.

- **Severity:** Medium 4.8 (`CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 17 Jul 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m9fc-6rj7-749h

## What is CVE-2017-3742?

CVE-2017-3742 is a medium-severity vulnerability in Lenovo Connect2, published on 17 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Lenovo Connect2 versions earlier than 4.2.5.4885 for Windows and 4.2.5.3071 for Android, when an ad-hoc connection is made between two systems for the purpose of sharing files, the password for this ad-hoc connection will be stored in a user-readable location. An attacker with read access to the user's contents could connect to the Connect2 hotspot and see the contents of files while they are being transferred between the two systems.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Lenovo Connect2.

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

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

## Is CVE-2017-3742 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3742 is a medium-severity vulnerability in Lenovo Connect2, published on 17 Jul 2017. 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-3742 in the wild and no public exploit code.

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

## Sources

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

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