Local file-existence disclosure via privileged config probe
Published Apr 14, 2022 · Updated Aug 3, 2024
Information disclosure in SWHKD 1.1.5 allows local users to test whether arbitrary root-readable files exist via the -c option. The privileged daemon's configuration loader opens the supplied path and exposes existence through distinct success and not-found behavior. Exploitation requires a local account and the permissive Polkit rule that runs the daemon as root; it reveals file existence but not file contents.
Summary
What happened
Information disclosure in SWHKD 1.1.5 allows local users to test whether arbitrary root-readable files exist via the -c option. The privileged daemon's configuration loader opens the supplied path and exposes existence through distinct success and not-found behavior. Exploitation requires a local account and the permissive Polkit rule that runs the daemon as root; it reveals file existence but not file contents.
The record
- CVE
- CVE-2022-27814
- Published
- Apr 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-203, T1083
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 14, 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.
Public exploit references
- oss-sec privileged-path existence testfunctional · 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