File integrity loss via unsafe temporary creation
Published Feb 7, 2020 · Updated Aug 6, 2024
Unsafe temporary-file creation in Linux Mint mintNanny as of 2012-03-19 allows attackers to affect file integrity via a temporary file. The cited locus is line 70 of mintNanny.py, where temporary-file creation lacks the secure tempfile.mkstemp primitive recommended by the disclosure. The public disclosure does not identify the execution context or exact data attackers can alter, leaving the access precondition and bounded integrity consequence unspecified.
Summary
What happened
Unsafe temporary-file creation in Linux Mint mintNanny as of 2012-03-19 allows attackers to affect file integrity via a temporary file. The cited locus is line 70 of mintNanny.py, where temporary-file creation lacks the secure tempfile.mkstemp primitive recommended by the disclosure. The public disclosure does not identify the execution context or exact data attackers can alter, leaving the access precondition and bounded integrity consequence unspecified.
The record
- CVE
- CVE-2012-1566
- Published
- Feb 7, 2020
- Updated
- Aug 6, 2024
- Vendor
- Linux Mint
- Product
- Linux Mint
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 7, 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=2012-03-19
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
No sourced classifications are available.
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