Local temporary-file interference
Published Jan 31, 2020 · Updated Aug 7, 2024
Temporary-file handling in Batch::BatchRun 1.03 allows local users to interfere with files created during batch execution. The archived disclosure identifies unsafe use of /tmp but does not disclose the affected routine, filename construction, or file-opening operation. Exploitation requires local access to shared temporary storage; public sources do not identify the resulting file modification or execution impact.
Summary
What happened
Temporary-file handling in Batch::BatchRun 1.03 allows local users to interfere with files created during batch execution. The archived disclosure identifies unsafe use of /tmp but does not disclose the affected routine, filename construction, or file-opening operation. Exploitation requires local access to shared temporary storage; public sources do not identify the resulting file modification or execution impact.
The record
- CVE
- CVE-2011-4117
- Published
- Jan 31, 2020
- Updated
- Aug 7, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- 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?
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
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