CVE-2022-24644
Published: 10 March 2022
Summary
CVE-2022-24644 is a high-severity Download of Code Without Integrity Check (CWE-494) vulnerability in Zzinc Keymouse Firmware. Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 6.5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
CVE-2022-24644 is a remote code execution vulnerability in ZZ Inc. KeyMouse for Windows versions 3.08 and earlier. It stems from an unauthenticated update mechanism that lacks integrity verification, corresponding to CWE-494, and carries a CVSS 3.1 score of 8.8 reflecting network attack vector, low complexity, no required privileges, and required user interaction.
An attacker can exploit the flaw when a user manually triggers an update on an affected installation, allowing the delivery of malicious code that executes with the privileges of the KeyMouse process and results in full compromise of confidentiality, integrity, and availability on the target system.
The EPSS score has remained flat at a peak of 0.1084 since disclosure, with no indication of rising exploitation interest. Public advisories and a detailed PDF are referenced at the vendor site and on GitHub, though specific mitigation steps such as patches are not described in the available data.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-29519
Vulnerability details
ZZ Inc. KeyMouse Windows 3.08 and prior is affected by a remote code execution vulnerability during an unauthenticated update. To exploit this vulnerability, a user must trigger an update of an affected installation of KeyMouse.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Policies can require integrity verification of software prior to installation, reducing risks from unverified downloads.
Blocks installation of components lacking a valid signature, mitigating download or installation of code without integrity checks.
Acquisition and maintenance portions of the strategy drive requirements for integrity verification of downloaded or supplied code.
Mandating integrity control and approved-only changes during development prevents incorporation of code or components lacking integrity validation.
Supply chain protection requires integrity verification of acquired components, directly reducing insertion or tampering of malicious code during delivery.
Reduces exposure to code obtained without integrity verification by requiring assurance processes that confirm authenticity and absence of tampering.
Tamper resistance and detection commonly include integrity verification of code and firmware obtained from external sources.
Component authenticity requires verifying origin/integrity of acquired firmware or software, directly preventing inclusion of code without integrity checks.