# CVE-2016-10761: Security feature bypass in n/a

> Attackers can inject keystrokes into Logitech Unifying devices by bypassing encryption, potentially executing arbitrary commands on the host system.

- **Severity:** Medium 6.5 (`CVSS:3.0/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:** 29 Jun 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xgph-v3ch-chmg

## What is CVE-2016-10761?

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

### Official description

Logitech Unifying devices before 2016-02-26 allow keystroke injection, bypassing encryption, aka MouseJack.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 5 products.


Products: Logitech K360 Firmware, Logitech K400r Firmware, Logitech K750 Firmware, Logitech K830 Firmware, Logitech Unifying Receiver Firmware.

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

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

## Is CVE-2016-10761 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-13055](https://insights.sbomify.com/CVE-2019-13055/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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