Local privilege escalation via reused temporary filename
Published Feb 26, 2022 · Updated Aug 3, 2024
Privilege escalation in KDE KCron 21.12.2 and earlier allows local users to run commands as another user through a temporary-file race. CTCron caches a QTemporaryFile name for the editing session, deletes the file after saving, and later reopens that path without O_EXCL or O_NOFOLLOW. After observing one save, an untrusted local user can race a symlink or controlled file before a later save, replacing user or system crontab content.
Summary
What happened
Privilege escalation in KDE KCron 21.12.2 and earlier allows local users to run commands as another user through a temporary-file race. CTCron caches a QTemporaryFile name for the editing session, deletes the file after saving, and later reopens that path without O_EXCL or O_NOFOLLOW. After observing one save, an untrusted local user can race a symlink or controlled file before a later save, replacing user or system crontab content.
The record
- CVE
- CVE-2022-24986
- Published
- Feb 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-668, CWE-362, T1053.003
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 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
- KCron temporary-file race procedureproof 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