Disclosure and startup interruption via fixed PID path
Published Mar 29, 2022 · Updated Aug 3, 2024
Insecure temporary-file handling in SWHKD 1.1.5 and earlier allows local users to disclose files or interrupt daemon startup. The root daemon reads, logs, and overwrites /tmp/swhkd.pid without preventing attacker-controlled pre-creation or symlink resolution. PID pre-creation blocks later starts; file disclosure and target-file overwrite require disabled kernel symlink protection.
Summary
What happened
Insecure temporary-file handling in SWHKD 1.1.5 and earlier allows local users to disclose files or interrupt daemon startup. The root daemon reads, logs, and overwrites /tmp/swhkd.pid without preventing attacker-controlled pre-creation or symlink resolution. PID pre-creation blocks later starts; file disclosure and target-file overwrite require disabled kernel symlink protection.
The record
- CVE
- CVE-2022-27815
- Published
- Mar 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-377, CWE-59, T1499, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 29, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Fixed PID pathname pre-creation and symlink demonstrationproof of concept · demonstrated
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