Local memory exhaustion via unbounded configuration parsing
Published Apr 7, 2022 · Updated Aug 3, 2024
Uncontrolled resource consumption in SWHKD 1.1.5 allows local users to exhaust memory by supplying a large file through the -c option. The privileged swhkd daemon reads and parses the named configuration file completely without a size limit or an effective privilege boundary. Any local user permitted to launch swhkd through pkexec can trigger high I/O and memory exhaustion with an infinite or block device, while specially formatted privileged files can disclose content.
Summary
What happened
Uncontrolled resource consumption in SWHKD 1.1.5 allows local users to exhaust memory by supplying a large file through the -c option. The privileged swhkd daemon reads and parses the named configuration file completely without a size limit or an effective privilege boundary. Any local user permitted to launch swhkd through pkexec can trigger high I/O and memory exhaustion with an infinite or block device, while specially formatted privileged files can disclose content.
The record
- CVE
- CVE-2022-27819
- Published
- Apr 7, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-770, T1499
- Attack vector
- local
- Privileges
- unauthenticated
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
- Block-device configuration parsing exampleproof 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