Hotkey disclosure and service interruption via fixed socket
Published Apr 7, 2022 · Updated Aug 3, 2024
Local resource hijacking in SWHKD before 1.2.0 allows local users to intercept hotkey commands or prevent hotkey processing. The privileged swhkd daemon connects to the fixed /tmp/swhkd.sock path, allowing a pre-created attacker socket to receive commands intended for swhks. Exploitation requires local filesystem and UNIX-socket access; the result is command disclosure or failure of the hotkey service to start and deliver events.
Summary
What happened
Local resource hijacking in SWHKD before 1.2.0 allows local users to intercept hotkey commands or prevent hotkey processing. The privileged swhkd daemon connects to the fixed /tmp/swhkd.sock path, allowing a pre-created attacker socket to receive commands intended for swhks. Exploitation requires local filesystem and UNIX-socket access; the result is command disclosure or failure of the hotkey service to start and deliver events.
The record
- CVE
- CVE-2022-27818
- Published
- Apr 7, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-668, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 7, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo