Privileged path manipulation via unchecked group-writable components
Published Oct 6, 2022 · Updated Sep 16, 2024
Incorrect authorization in chkstat in SUSE and openSUSE Linux products allows local users to influence privileged binary path resolution. The safeOpen() validation accepts paths whose parent directories or target files are group-writable instead of rejecting group-controlled components. Exploitation requires group write access to such a component and permits substitution along a privileged binary path; no guaranteed privilege-escalation outcome is documented.
Summary
What happened
Incorrect authorization in chkstat in SUSE and openSUSE Linux products allows local users to influence privileged binary path resolution. The safeOpen() validation accepts paths whose parent directories or target files are group-writable instead of rejecting group-controlled components. Exploitation requires group write access to such a component and permits substitution along a privileged binary path; no guaranteed privilege-escalation outcome is documented.
The record
- CVE
- CVE-2022-31252
- Published
- Oct 6, 2022
- Updated
- Sep 16, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Leap
- Classifications
- CWE-863, T1574
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 6, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=permissions <20200127
- Affected versionversion=permissions <20201225
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.
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