Root-level arbitrary file deletion
Published Jan 15, 2020 · Updated Aug 6, 2024
File deletion in Canonical Whoopsie before 0.1.26 allows local users with root privileges to remove arbitrary files. Canonical's public record does not identify the affected function, path operation, or attacker-controlled filename. Exploitation requires root-level access, and the documented consequence is file deletion rather than disclosure or code execution.
Summary
What happened
File deletion in Canonical Whoopsie before 0.1.26 allows local users with root privileges to remove arbitrary files. Canonical's public record does not identify the affected function, path operation, or attacker-controlled filename. Exploitation requires root-level access, and the documented consequence is file deletion rather than disclosure or code execution.
The record
- CVE
- CVE-2012-0945
- Published
- Jan 15, 2020
- Updated
- Aug 6, 2024
- Vendor
- Canonical
- Product
- Whoopsie
- Classifications
- CWE-428, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=< 0.1.26
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