Local root escalation via insecure temporary file
Published Feb 25, 2021 · Updated Sep 16, 2024
Insecure temporary file handling in openSUSE Factory cyrus-sasl through 2.1.27-4.2 allows local users to escalate to root. The packaging used /tmp for update scripts in a way that permitted unsafe temporary-file manipulation; the fix moves scripts to /var/adm/update-scripts and cleans them up. Exploitation requires local access, and successful abuse can grant root privileges with resulting confidentiality, integrity, and availability impact.
Summary
What happened
Insecure temporary file handling in openSUSE Factory cyrus-sasl through 2.1.27-4.2 allows local users to escalate to root. The packaging used /tmp for update scripts in a way that permitted unsafe temporary-file manipulation; the fix moves scripts to /var/adm/update-scripts and cleans them up. Exploitation requires local access, and successful abuse can grant root privileges with resulting confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2020-8032
- Published
- Feb 25, 2021
- Updated
- Sep 16, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Factory
- Classifications
- CWE-377, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 25, 2021CVE 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=cyrus-sasl <=2.1.27-4.2
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