LiveActive security incident?Get immediate response
CVE Record

CVE-2010-1184: The Microsoft wireless keyboard uses XOR encryption with a key derived from the MAC address, which makes it...

The Microsoft wireless keyboard uses XOR encryption with a key derived from the MAC address, which makes it easier for remote attackers to obtain keystroke information and inject arbitrary commands via a nearby wireless device, as demonstrated by Keykeriki 2.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2010-1184 describes weak encryption in a Microsoft wireless keyboard. Keystrokes could be read, and commands could be injected, by an attacker close enough to communicate wirelessly. The practical risk is highest where older Microsoft wireless keyboards are still used for sensitive workstations. Exposure is limited to environments still using the affected class of Microsoft wireless keyboards. Risk requires attacker proximity to the keyboard’s wireless signal. Exact models and versions are not specified in the provided sources, so asset confirmation may require physical inventory and vendor documentation. Treat this as a targeted physical-proximity risk, not an internet-wide emergency. Prioritize replacement where sensitive credentials, privileged access, or confidential data entry occurs. Because the affected models are unclear, the fastest control is inventory and removal from critical workstations. Mitigation focus: Identify and remove potentially affected Microsoft wireless keyboards from sensitive environments.; Prefer wired keyboards or modern wireless keyboards with documented strong encryption.; Check Microsoft or device vendor guidance for model-specific replacement or mitigation advice..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2010-1184 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.