Local application crash via predictable temporary directory
Published Mar 23, 2020 · Updated Aug 4, 2024
Predictable temporary directory creation in Zim 0.42-beta1 through 0.72.1 allows local users to crash the application. At startup, Zim derives /tmp/zim-USER from the account name and calls os.chmod() on an existing path without verifying its ownership, so an attacker-owned directory makes the permission change fail. Exploitation requires another local account able to create the victim's directory first in world-writable /tmp, and the bounded consequence is failure to start Zim.
Summary
What happened
Predictable temporary directory creation in Zim 0.42-beta1 through 0.72.1 allows local users to crash the application. At startup, Zim derives /tmp/zim-USER from the account name and calls os.chmod() on an existing path without verifying its ownership, so an attacker-owned directory makes the permission change fail. Exploitation requires another local account able to create the victim's directory first in world-writable /tmp, and the bounded consequence is failure to start Zim.
The record
- CVE
- CVE-2020-10870
- Published
- Mar 23, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-330, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 23, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
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