Local arbitrary file overwrite via predictable temp filenames
Published Jan 31, 2020 · Updated Aug 7, 2024
Insecure temporary-file handling in Parallel::ForkManager before 1.0.0 allows local users to overwrite arbitrary files through symlinks. The module serializes child-returned data to predictable PID-based filenames and follows attacker-created links when writing those files. Exploitation requires an attacker-writable temporary directory and writes with the privileges of the process using the module.
Summary
What happened
Insecure temporary-file handling in Parallel::ForkManager before 1.0.0 allows local users to overwrite arbitrary files through symlinks. The module serializes child-returned data to predictable PID-based filenames and follows attacker-created links when writing those files. Exploitation requires an attacker-writable temporary directory and writes with the privileges of the process using the module.
The record
- CVE
- CVE-2011-4115
- Published
- Jan 31, 2020
- Updated
- Aug 7, 2024
- Vendor
- Parallel::ForkManager
- Product
- Parallel::ForkManager
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 31, 2020CVE publishedPublication date reported by the CVE source.
- Aug 7, 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=before 1.0.0
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