# CVE-2016-1491: Hardcoded credentials in n/a

> Lenovo SHAREit uses a hardcoded password for its hotspot, allowing remote attackers to gain access when file receiving is enabled.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xf4x-rm5j-3f4c

## What is CVE-2016-1491?

CVE-2016-1491 is a high-severity vulnerability in n/a, published on 26 Jan 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Wifi hotspot in Lenovo SHAREit before 3.2.0 for Windows, when configured to receive files, has a hardcoded password of 12345678, which makes it easier for remote attackers to obtain access by leveraging a position within the WLAN coverage area.

Weakness: CWE-255

## Which versions are affected by CVE-2016-1491?

It affects 1 product.


Products: Lenovo Shareit.

## How do I fix CVE-2016-1491?

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

## Is CVE-2016-1491 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-4782](https://insights.sbomify.com/CVE-2016-4782/): Other in n/a (high 8.8)
- [CVE-2016-1489](https://insights.sbomify.com/CVE-2016-1489/): Information disclosure in n/a (high 8.0)
- [CVE-2016-4783](https://insights.sbomify.com/CVE-2016-4783/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2016-1492](https://insights.sbomify.com/CVE-2016-1492/): Auth bypass in n/a (medium 6.1)
- [CVE-2016-1490](https://insights.sbomify.com/CVE-2016-1490/): Information disclosure in n/a (medium 4.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1491 and fix it if it is affected.

What it is: CVE-2016-1491 is a high-severity vulnerability in n/a, published on 26 Jan 2016. 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-2016-1491 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-2016-1491/ (Markdown: https://insights.sbomify.com/CVE-2016-1491/index.md)
```

## Sources

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

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