Local code execution via insecure temporary files
Published Oct 26, 2021 · Updated Aug 7, 2024
Insecure temporary-file handling in INRIA Caml Light 0.75 and earlier allows local users to overwrite files or execute code. The camlyacc create_file_names routine calls mktemp() before reopening four names with fopen(), while the install target writes, chmods, and executes the fixed /tmp/testscr path. Exploitation requires another local user to invoke camlyacc or run make install with elevated privileges; the latter path can execute attacker-controlled content with installer privileges.
Summary
What happened
Insecure temporary-file handling in INRIA Caml Light 0.75 and earlier allows local users to overwrite files or execute code. The camlyacc create_file_names routine calls mktemp() before reopening four names with fopen(), while the install target writes, chmods, and executes the fixed /tmp/testscr path. Exploitation requires another local user to invoke camlyacc or run make install with elevated privileges; the latter path can execute attacker-controlled content with installer privileges.
The record
- CVE
- CVE-2011-4119
- Published
- Oct 26, 2021
- Updated
- Aug 7, 2024
- Vendor
- INRIA
- Product
- Caml Light
- Classifications
- CWE-377, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 26, 2021CVE 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=caml-light <= 0.75
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
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