Service interruption via predictable debug-file path
Published Mar 16, 2022 · Updated Sep 17, 2024
Insecure temporary-file handling in openSUSE Factory cscreen 1.3 and earlier allows local users to interrupt cscreen or the system. The cscreen startup script writes debugging output to the predictable /tmp/cscreen.debug path instead of creating a uniquely named, protected file. A local user can preposition that path to disrupt cscreen; system-wide interruption requires a non-default configuration.
Summary
What happened
Insecure temporary-file handling in openSUSE Factory cscreen 1.3 and earlier allows local users to interrupt cscreen or the system. The cscreen startup script writes debugging output to the predictable /tmp/cscreen.debug path instead of creating a uniquely named, protected file. A local user can preposition that path to disrupt cscreen; system-wide interruption requires a non-default configuration.
The record
- CVE
- CVE-2022-21945
- Published
- Mar 16, 2022
- Updated
- Sep 17, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Factory
- Classifications
- CWE-377, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=cscreen <=1.2-1.3
What conditions does exploitation require?
What is affected?
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