# CVE-2016-6257: Weak cryptography in n/a

> Remote attackers can inject encrypted keyboard input into systems using vulnerable Lenovo wireless dongles due to improper AES counter implementation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 2 Aug 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mjv4-gqjq-h75g

## What is CVE-2016-6257?

CVE-2016-6257 is a medium-severity vulnerability in n/a, published on 2 Aug 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The firmware in Lenovo Ultraslim dongles, as used with Lenovo Liteon SK-8861, Ultraslim Wireless, and Silver Silk keyboards and Liteon ZTM600 and Ultraslim Wireless mice, does not enforce incrementing AES counters, which allows remote attackers to inject encrypted keyboard input into the system by leveraging proximity to the dongle, aka a "KeyJack injection attack."

Weakness: CWE-310

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

It affects 5 products.


Products: Amazonbasics Firmware, Dell Km632 Firmware, Dell Km714 Firmware, Lenovo Ultraslim Firmware, Logitech Unifying Firmware.

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

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

## Is CVE-2016-6257 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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