Microsoft Wireless Keyboard 850 Security Feature AES cryptographic issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.66 |
Summary
A vulnerability was found in Microsoft Wireless Keyboard 850. It has been classified as critical. This affects an unknown function of the component Security Feature. The manipulation leads to cryptographic issue (AES). This vulnerability is referenced as CVE-2018-8117. It is possible to launch the attack on the physical device. No exploit is available. It is recommended to apply a patch to fix this issue.
Details
A vulnerability was found in Microsoft Wireless Keyboard 850 (Forum Software). It has been rated as critical. This issue affects an unknown code block of the component Security Feature. The manipulation with an unknown input leads to a cryptographic issue vulnerability (AES). Using CWE to declare the problem leads to CWE-310. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The bug was discovered 04/10/2018. The weakness was published 04/10/2018 with Microsoft as confirmed security update guide (Website). It is possible to read the advisory at portal.msrc.microsoft.com. The identification of this vulnerability is CVE-2018-8117 since 03/14/2018. Attacking locally is a requirement. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK. The advisory points out:
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. An attacker would first have to extract the AES encryption key from the affected keyboard device. The attacker would also need to maintain physical proximity – within wireless range – of the devices for the duration of the attack.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 103711†). Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: AESClass: Cryptographic issue / AES
CWE: CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
03/14/2018 🔍04/10/2018 🔍
04/10/2018 🔍
04/10/2018 🔍
04/10/2018 🔍
04/11/2018 🔍
04/13/2018 🔍
02/09/2021 🔍
Sources
Vendor: microsoft.comAdvisory: portal.msrc.microsoft.com
Researcher: Microsoft
Organization: Microsoft
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-8117 (🔍)
GCVE (CVE): GCVE-0-2018-8117
GCVE (VulDB): GCVE-100-116135
SecurityFocus: 103711 - Microsoft Wireless Keyboard CVE-2018-8117 Local Security Bypass Vulnerability
Entry
Created: 04/13/2018 10:10Updated: 02/09/2021 18:53
Changes: 04/13/2018 10:10 (64), 01/24/2020 16:55 (5), 02/09/2021 18:53 (2)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.