# CVE-2018-8117: Security feature bypass in Microsoft Wireless Keyboard 850

> Attackers can bypass security features to reuse AES keys, allowing them to inject keystrokes or read data from Microsoft Wireless Keyboard 850 devices.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/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:** 12 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3m6p-3rc3-w9wf

## What is CVE-2018-8117?

CVE-2018-8117 is a medium-severity vulnerability in Microsoft Wireless Keyboard 850, published on 12 Apr 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security feature bypass vulnerability exists in the Microsoft Wireless Keyboard 850 which could allow an attacker to reuse an AES encryption key to send keystrokes to other keyboard devices or to read keystrokes sent by other keyboards for the affected devices, aka "Microsoft Wireless Keyboard 850 Security Feature Bypass Vulnerability." This affects Microsoft Wireless Keyboard 850.

## Which versions are affected by CVE-2018-8117?

It affects 1 product.


Products: Microsoft Wireless Keyboard 850.

## How do I fix CVE-2018-8117?

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

## Is CVE-2018-8117 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8117 and fix it if it is affected.

What it is: CVE-2018-8117 is a medium-severity vulnerability in Microsoft Wireless Keyboard 850, published on 12 Apr 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-2018-8117 in the wild and no public exploit code.

Affected product: Microsoft Wireless Keyboard 850. 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-2018-8117/ (Markdown: https://insights.sbomify.com/CVE-2018-8117/index.md)
```

## Sources

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

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